Triple
T677999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southeast Division |
E13119
|
entity |
| Predicate | conferenceDivisionType |
P11735
|
FINISHED |
| Object | Eastern Conference 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: Eastern Conference division | Statement: [Southeast Division, conferenceDivisionType, Eastern Conference division]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conferenceDivisionType Context triple: [Southeast Division, conferenceDivisionType, Eastern Conference division]
-
A.
NCAADivision
Indicates the competitive division within the NCAA in which an institution or team participates.
-
B.
teamDivision
Indicates how a larger team is split into smaller subgroups or units for organization or collaboration.
-
C.
competesInDivision
chosen
Indicates that an entity participates in competitive activities within a specified division or tier of a larger organizational or league structure.
-
D.
teamDivisionControlled
Indicates that one entity has authority over or manages the organizational structure or division of a team.
-
E.
isDivisionalMatchup
Indicates that the two entities (typically teams) are competing against each other within the same division.
- 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_69a4933d3bf88190972041cd8cf143b9 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a04c89148190b6330e86697bb37b |
completed | March 1, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69a49d1bbd0c81909cfbec30bd17bde7 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.