Triple
T5939053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA Division I Men’s Golf Championship |
E132117
|
entity |
| Predicate | formatChangeEffectiveFrom |
P27688
|
FINISHED |
| Object | 2009 |
—
|
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: 2009 | Statement: [NCAA Division I Men’s Golf Championship, formatChangeEffectiveFrom, 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatChangeEffectiveFrom Context triple: [NCAA Division I Men’s Golf Championship, formatChangeEffectiveFrom, 2009]
-
A.
formatMayChange
Indicates that the format or structure of something is subject to modification and may not remain consistent over time.
-
B.
mostRecentFormatChange
chosen
Indicates the most recent modification made to the format or structure of an entity, relative to all prior format changes.
-
C.
startDateChangedTo
Indicates that the start date of something has been modified from its previous value to a new specified date.
-
D.
dateChangesWith
Indicates that the date associated with one entity is altered or updated in conjunction with, or as a result of, a change involving another entity.
-
E.
nameChangeDate
Indicates the date on which an entity’s name was officially changed.
- 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_69c0085c55dc8190aa90e242c956e2fa |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03f26f51881908cc253fe5775a1fc |
completed | March 22, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69c03355caf08190b960563a1aed23f9 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:01 p.m.