Triple
T79257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | College Football Playoff |
E1589
|
entity |
| Predicate | tieBreakingCriteria |
P136
|
FINISHED |
| Object | head-to-head results |
—
|
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: head-to-head results | Statement: [College Football Playoff, tieBreakingCriteria, head-to-head results]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tieBreakingCriteria Context triple: [College Football Playoff, tieBreakingCriteria, head-to-head results]
-
A.
selectionCriteria
chosen
Indicates the conditions or rules used to choose certain entities from a larger set.
-
B.
awardCriteria
Indicates the standards or conditions used to determine eligibility for receiving an award or recognition.
-
C.
confersPrecedenceIn
Indicates that one entity is granted higher priority, rank, or standing over another within a specified context or domain.
-
D.
crossType
Indicates a relationship where one entity intersects, passes over, or traverses another, typically implying movement or extension across a boundary, area, or medium.
-
E.
eligibilityCriteria
Indicates the conditions or requirements that must be satisfied for an entity to qualify for or be considered eligible for something.
- 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_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. |
Created at: Feb. 28, 2026, 2:06 a.m.