Triple
T6106614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amen Corner |
E136131
|
entity |
| Predicate | hasHoleNumberRange |
P68178
|
FINISHED |
| Object | 11–13 |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 11–13 | Statement: [Amen Corner, hasHoleNumberRange, 11–13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHoleNumberRange Context triple: [Amen Corner, hasHoleNumberRange, 11–13]
-
A.
hasHoleCount
Indicates that an entity possesses a specified number of holes.
-
B.
numberOfHoles
Indicates the count of holes associated with or present in a given entity.
-
C.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
D.
hasShipNumberRange
Indicates that an entity is associated with ships whose identification numbers fall within a specified numeric range.
-
E.
hasDayNumberRange
Indicates that something is associated with a contiguous range of day numbers between a specified minimum and maximum value.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69c0087dee9881909e3655be88208c01 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b806bd48190b6f020af3391adb8 |
completed | March 22, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c049f80e2081909b7d84a104cda68d |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8e3f2c8190be459ca02f9b315a |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:13 p.m.