Triple
T919390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | San Diego Sails |
E19847
|
entity |
| Predicate | successorLeagueContext |
P16227
|
FINISHED |
| Object | predecessor to NBA–ABA merger |
—
|
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: predecessor to NBA–ABA merger | Statement: [San Diego Sails, successorLeagueContext, predecessor to NBA–ABA merger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorLeagueContext Context triple: [San Diego Sails, successorLeagueContext, predecessor to NBA–ABA merger]
-
A.
successorContext
chosen
Indicates that one context directly follows and continues from another in a sequence or process.
-
B.
successorCompetition
Indicates that one competition directly follows another in sequence, serving as its successor in a series or timeline.
-
C.
successorCategory
Indicates that one category directly follows or replaces another in an ordered sequence or hierarchy.
-
D.
successorDivision
Indicates that one division is the organizational successor that continues or replaces the role, functions, or identity of another division.
-
E.
successorLine
Indicates that one line directly follows another in a sequence or ordered arrangement.
- 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_69a493a099788190a696d9d8408cbaf4 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b388f0bc8190a087222636135ba5 |
completed | March 1, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69a4b2944ff88190a260be5355132ba5 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.