Triple
T919194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky Colonels |
E19842
|
entity |
| Predicate | didNotJoin |
P3971
|
FINISHED |
| Object | 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: NBA–ABA merger | Statement: [Kentucky Colonels, didNotJoin, NBA–ABA merger]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: didNotJoin Context triple: [Kentucky Colonels, didNotJoin, NBA–ABA merger]
-
A.
didNotHold
Indicates that an expected event, condition, or relationship failed to occur or be valid.
-
B.
doesNotParticipateIn
chosen
Indicates that an entity is explicitly not involved in, associated with, or taking part in a specified activity, event, or process.
-
C.
notAwardedFor
Indicates that a particular award, prize, or honor was explicitly not given in recognition of a specified work, achievement, or entity.
-
D.
notAwardedIn
Indicates that a particular award or recognition was not given to an entity within a specified context, such as a year, event, or category.
-
E.
didNotOverrule
Indicates that one entity, typically a higher authority or court, chose not to overturn, reverse, or invalidate the decision or ruling made by another entity.
- 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.