Triple
T2571888
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CFL |
E57681
|
entity |
| Predicate | codeOfFootball |
P24689
|
FINISHED |
| Object | Canadian code of gridiron football |
—
|
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: Canadian code of gridiron football | Statement: [CFL, codeOfFootball, Canadian code of gridiron football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeOfFootball Context triple: [CFL, codeOfFootball, Canadian code of gridiron football]
-
A.
FIFAcode
Indicates the standardized three-letter country or territory code assigned by FIFA to represent a national football team in international competitions.
-
B.
league2
Indicates that an entity participates in, is a member of, or is otherwise affiliated with a specific sports league or competitive organization.
-
C.
typeOfFootball
chosen
Indicates the specific code or variant of football that characterizes or classifies a given football-related entity.
-
D.
playedAssociationFootball
Indicates that an entity has participated in playing the sport of association football (soccer).
-
E.
leagueCup
Indicates that an entity is a cup-style competition organized within or by a specific league.
- 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_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. |
Created at: March 6, 2026, 9:48 p.m.