Triple
T9339805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL tiebreaking procedures |
E224734
|
entity |
| Predicate | finalResortCriterion |
P35633
|
FINISHED |
| Object | coin toss |
—
|
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: coin toss | Statement: [NFL tiebreaking procedures, finalResortCriterion, coin toss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalResortCriterion Context triple: [NFL tiebreaking procedures, finalResortCriterion, coin toss]
-
A.
primaryCriterion
Indicates that one factor is designated as the main or most important basis for a decision, judgment, or selection among alternatives.
-
B.
decisionBasis
Indicates the underlying reason, criterion, or rationale on which a decision is made.
-
C.
finalSiteSelection
Indicates the decision or confirmation that a particular site has been chosen as the final location from among candidate options.
-
D.
resultDetermination
Indicates the process or criteria by which an outcome, decision, or result is established or concluded from given inputs or conditions.
-
E.
decisionMakingRule
chosen
Indicates the principle, guideline, or procedure that governs how a decision is made in a given context.
- 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.