Triple
T12244514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Players Championship |
E291817
|
entity |
| Predicate | yardage |
P34478
|
FINISHED |
| Object | approximately 7250 yards |
—
|
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: approximately 7250 yards | Statement: [The Players Championship, yardage, approximately 7250 yards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yardage Context triple: [The Players Championship, yardage, approximately 7250 yards]
-
A.
hasYard
Indicates that one entity possesses or includes a yard as part of its property or premises.
-
B.
hasYardage
chosen
Indicates that something possesses or is associated with a specific measured distance or length, typically expressed in yards.
-
C.
yardsPerCarry
Indicates the average number of yards gained per rushing attempt in a running play.
-
D.
yardLine
Indicates the specific position on a football field, measured in yards from a reference goal line, where a play or event occurs.
-
E.
hasGoodsYard
Indicates that a location or facility includes or is equipped with a goods yard for handling freight or cargo.
- F. None of above.
Provenance (3 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d38ee10819093ed41d2954bf4ef |
completed | April 10, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69d91c46dcd88190a263db30804bff36 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:51 p.m.