Triple
T9339817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL tiebreaking procedures |
E224734
|
entity |
| Predicate | evolvedWith |
P87600
|
FINISHED |
| Object | changes to playoff format |
—
|
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: changes to playoff format | Statement: [NFL tiebreaking procedures, evolvedWith, changes to playoff format]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evolvedWith Context triple: [NFL tiebreaking procedures, evolvedWith, changes to playoff format]
-
A.
evolvedIn
Indicates that an entity originated or developed within a specified environment, context, or location over evolutionary time.
-
B.
evolvesIn
Indicates that an entity undergoes a process of change or development within a specified environment, context, or medium.
-
C.
evolvesAcross
Indicates a transformation or development of one entity into another across different states, stages, or contexts.
-
D.
evolves
Indicates that one entity undergoes a process of gradual change or development into another, typically more advanced or different, state or form.
-
E.
laterTeamEvolvedInto
Indicates that a team existing at a later time transformed, rebranded, or otherwise changed into another team as its successor.
- 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_69ca84286fcc81909f6e7fd7a7e862a2 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4bae2e2481909effc2dc89a642c5 |
completed | April 1, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69cc7a66aef08190b8d668cff5b04f5f |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc94b796788190816b71b1e9996288 |
completed | April 1, 2026, 3:44 a.m. |
Created at: March 30, 2026, 7:40 p.m.