Triple
T12375108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA Eastern Conference |
E295101
|
entity |
| Predicate | introducedDivisions |
P104642
|
FINISHED |
| Object | 1970–71 NBA season |
—
|
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: 1970–71 NBA season | Statement: [NBA Eastern Conference, introducedDivisions, 1970–71 NBA season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedDivisions Context triple: [NBA Eastern Conference, introducedDivisions, 1970–71 NBA season]
-
A.
includesDivisions
Indicates that one entity contains or encompasses one or more subordinate divisions or sections within it.
-
B.
modernDivision
Indicates that one entity is a contemporary or currently recognized administrative or organizational subdivision of another entity.
-
C.
capitalDivision
Indicates that one administrative division serves as the capital of another administrative division or political entity.
-
D.
historicallyDividedInto
Indicates that an entity was separated into multiple distinct parts or regions during a past historical period.
-
E.
traditionallyDividedInto
Indicates that something is customarily or historically separated into specific parts, sections, or categories according to established tradition.
- 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_69d6ab6d8a4081908636601e69ddf262 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93fa8ca7c8190b3f8e9c2ec23e837 |
completed | April 10, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_69d93ed256788190b704cad171a4824e |
completed | April 10, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69d93fa244148190a960be3ff6f1cf45 |
completed | April 10, 2026, 6:21 p.m. |
Created at: April 8, 2026, 9:54 p.m.