Triple
T1640175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Division |
E35450
|
entity |
| Predicate | conferenceRealignment |
P29739
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [Central Division, conferenceRealignment, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceRealignment Context triple: [Central Division, conferenceRealignment, 2013]
-
A.
conferenceAlignment
Indicates how closely a conference’s themes, goals, or content correspond to a particular standard, interest, or strategic objective.
-
B.
divisionRealignment
Indicates a reorganization of how entities are grouped into divisions, typically involving changes to which entities belong to which division.
-
C.
competitionConference
Indicates that a competition is associated with, held at, or organized as part of a particular conference.
-
D.
otherConference
Indicates that one conference is distinct from and not the same as another conference.
-
E.
conference2
Indicates that one entity is a conference or event that is associated with, hosted by, or otherwise related to another entity.
- 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_69a88604618c81908b41f6429c431eb6 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a919306fd48190a245fc95e0e759d9 |
completed | March 5, 2026, 5:48 a.m. |
| PD | Predicate disambiguation | batch_69a907cc9d348190b76b0d3f596e5a81 |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a9192f975c8190bfd514a4b5a8786c |
completed | March 5, 2026, 5:48 a.m. |
Created at: March 4, 2026, 7:28 p.m.