Triple
T1146691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Basketball Association |
E23581
|
entity |
| Predicate | mergerEffectiveSeason |
P6607
|
FINISHED |
| Object | 1976–77 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: 1976–77 NBA season | Statement: [American Basketball Association, mergerEffectiveSeason, 1976–77 NBA season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergerEffectiveSeason Context triple: [American Basketball Association, mergerEffectiveSeason, 1976–77 NBA season]
-
A.
leagueMergerAfterSeasonWith
chosen
Indicates that two or more leagues merged into a single league following the completion of a specified season.
-
B.
mergerYear
Indicates the year in which two or more entities formally merged into a single entity.
-
C.
mergerResult
Indicates that one or more entities have combined into a single entity, specifying the outcome or resulting entity of the merger.
-
D.
mergerType
Indicates the specific kind or category of merger relationship that exists between the involved entities.
-
E.
mergerPartner
Indicates that two entities are involved as counterparties in a merger transaction with each other.
- 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bd0bed00819091d71983d787a030 |
completed | March 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4ee3988190ac89c5ae5b10e316 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.