Triple
T79263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | College Football Playoff |
E1589
|
entity |
| Predicate | replacedSystemUsedUntil |
P3618
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [College Football Playoff, replacedSystemUsedUntil, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedSystemUsedUntil Context triple: [College Football Playoff, replacedSystemUsedUntil, 2013]
-
A.
wasSupersededBy
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
B.
usedAt
Indicates that something is employed, applied, or utilized at a particular place, time, or context.
-
C.
usedSince
Indicates that an entity has been in use starting from a specified point in time and continuing thereafter.
-
D.
historicallyUsedFor
Indicates that something served a particular function or purpose at some point in the past, even if it may no longer be used that way now.
-
E.
inUseSince
Indicates that an entity has been actively in use starting from a specified point in time.
- 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_69a24c60d19c8190a1b6c105ca59ef5b |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a24fd16c248190a6ee4cd96c388772 |
completed | Feb. 28, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69a24eb126b48190b410b859c1be99aa |
completed | Feb. 28, 2026, 2:10 a.m. |
| PDg | Predicate description generation | batch_69a24fcfff7c8190adbacd1539829850 |
completed | Feb. 28, 2026, 2:15 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.