Triple
T2012139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Road Hole |
E43710
|
entity |
| Predicate | hasYardage |
P34478
|
FINISHED |
| Object | over 450 yards in championship setup |
—
|
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: over 450 yards in championship setup | Statement: [Road Hole, hasYardage, over 450 yards in championship setup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYardage Context triple: [Road Hole, hasYardage, over 450 yards in championship setup]
-
A.
fairwayType
Indicates the specific kind or classification of a fairway associated with an entity.
-
B.
typicalWinningScoreRelativeToPar
Indicates the usual or expected winning score in relation to the course’s par (e.g., how many strokes under or over par typically wins).
-
C.
hasGolfCourse
Indicates that one entity possesses, contains, or includes a golf course as part of its facilities or attributes.
-
D.
trailLengthApprox
Indicates an approximate measurement of the total length of a trail.
-
E.
hasMeasurementMarkings
Indicates that one entity bears visible measurement indicators or scale markings on its surface for quantifying something.
- 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_69a88716e9f08190946313fdc949e3cf |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb8b2ed6c8190ad51f0af90db2a02 |
completed | March 7, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69abb7a03a1c81909ad50d56667db2d5 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb83e7888819096dc40275c77daff |
completed | March 7, 2026, 5:31 a.m. |
Created at: March 4, 2026, 7:37 p.m.