Triple
T2571911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CFL |
E57681
|
entity |
| Predicate | hasRuleDifferenceFromNFL |
P39866
|
FINISHED |
| Object | larger field |
—
|
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: larger field | Statement: [CFL, hasRuleDifferenceFromNFL, larger field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRuleDifferenceFromNFL Context triple: [CFL, hasRuleDifferenceFromNFL, larger field]
-
A.
hasDesignatedPlayerRule
Indicates that a sports league or competition uses a designated player rule allowing certain players to be treated differently for roster or salary purposes.
-
B.
associatedLeagueRuleAdoption
Indicates that there is a connection between an entity and the specific league rule adoption that governs or influences it.
-
C.
isGridironFootballLeague
Indicates that the subject is a league or organized competition specifically for gridiron football.
-
D.
notableRuleChange
Indicates a significant modification to an established rule or set of rules that meaningfully alters how they apply or are enforced.
-
E.
hasRulebook
Indicates that one entity possesses, is governed by, or is associated with a specific rulebook.
- 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_69ab4a51410081908501dcf8bad9adc4 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd383dce881909411a38c6d37bc3a |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0ce4dcc8190b17a65abf9bd1bb0 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd251b48c8190862c7b39ea1bf8ea |
completed | March 7, 2026, 7:22 a.m. |
Created at: March 6, 2026, 9:48 p.m.