Triple
T1132464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantic Division |
E23061
|
entity |
| Predicate | divisionTitleImpact |
P23822
|
FINISHED |
| Object | used as tiebreaker for playoff seeding |
—
|
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: used as tiebreaker for playoff seeding | Statement: [Atlantic Division, divisionTitleImpact, used as tiebreaker for playoff seeding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionTitleImpact Context triple: [Atlantic Division, divisionTitleImpact, used as tiebreaker for playoff seeding]
-
A.
divisionTitle
Indicates the formal name or title assigned to a specific division within a larger organization or structure.
-
B.
divisionTitles
Indicates that an entity holds or is associated with one or more titles or championships within a specific division or category.
-
C.
divisionTitleCount
Indicates the number of titles or championships associated with a particular division.
-
D.
divisionAssociation
Indicates an organizational relationship where one entity functions as a division, branch, or sub-unit of another entity.
-
E.
rankingImpact
chosen
Indicates how an entity’s position or level in a ranking is affected or influenced by another factor or action.
- 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_69a493ec75988190b63a11bafaec29b4 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb48de2081909a0dce005b1c9df1 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.