Triple
T19574396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Football League |
E489812
|
entity |
| Predicate | ruleVariationFromNFL |
P67886
|
FINISHED |
| Object | overtime rules |
—
|
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: overtime rules | Statement: [United Football League, ruleVariationFromNFL, overtime rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ruleVariationFromNFL Context triple: [United Football League, ruleVariationFromNFL, overtime rules]
-
A.
hasRuleDifferenceFromNFL
Indicates that the subject’s rules differ in some way from those used in the NFL.
-
B.
rulesVariantOf
chosen
Indicates that one set of rules is a modified or alternative version derived from another set of rules.
-
C.
tacklesNFL
Indicates that one player forcefully brings another player to the ground or stops their forward progress in the context of an NFL play.
-
D.
jerseyNumberRules
Indicates rules or constraints governing which jersey numbers may be assigned or used.
-
E.
nflRecord
Indicates the win-loss-tie performance record a team or individual has accumulated in NFL competition.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6402333dc8190bdffb1da68e2c76b |
completed | April 20, 2026, 3:02 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:42 p.m.