Triple
T9339806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL tiebreaking procedures |
E224734
|
entity |
| Predicate | hasSeparatePath |
P27773
|
FINISHED |
| Object | two‑team tiebreakers |
—
|
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: two‑team tiebreakers | Statement: [NFL tiebreaking procedures, hasSeparatePath, two‑team tiebreakers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeparatePath Context triple: [NFL tiebreaking procedures, hasSeparatePath, two‑team tiebreakers]
-
A.
hasSeparateUnit
Indicates that one entity exists or is treated as an independent, distinct unit from another entity.
-
B.
hasMultipleSegments
Indicates that the referenced entity is composed of more than one distinct segment or section.
-
C.
hasSeparator
Indicates that one entity includes, uses, or is divided by another entity that serves as a separator or delimiting element.
-
D.
usesSeparateChannelFor
Indicates that one entity communicates with or accesses another entity through a distinct, dedicated channel separate from other communications or interactions.
-
E.
hasPathway
chosen
Indicates that there exists a route, channel, or sequence of steps through which one entity leads, connects, or gives access to another.
- 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_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. |
Created at: March 30, 2026, 7:40 p.m.