Triple
T10818373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CFL East Division |
E255292
|
entity |
| Predicate | hasConferenceType |
P95912
|
FINISHED |
| Object | geographical division |
—
|
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: geographical division | Statement: [CFL East Division, hasConferenceType, geographical division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConferenceType Context triple: [CFL East Division, hasConferenceType, geographical division]
-
A.
hasConference
Indicates that an entity organizes, hosts, or is associated with a specific conference.
-
B.
hasConferenceSchedule
Indicates that an entity possesses or is associated with a defined schedule for a conference, detailing its planned sessions or events.
-
C.
hasConferenceCode
Indicates that a conference is associated with a specific identifying code.
-
D.
hasConferenceOrDivision
Indicates that an entity is associated with a specific conference or division within a larger organizational or competitive structure.
-
E.
hasConferenceOfParties
Indicates that an entity is associated with or holds a Conference of the Parties (COP) as its formal decision-making or governing body.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7344866f88190be4addb7c8020fce |
completed | April 9, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69d70d1bf3648190b36fa96ea018e0dc |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d7101c96708190808fef73199e8482 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:18 p.m.