Triple
T20643718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1950–51 NBA season |
E507295
|
entity |
| Predicate | precededByMerger |
P140890
|
FINISHED |
| Object | BAA–NBL merger of 1949 |
—
|
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: BAA–NBL merger of 1949 | Statement: [1950–51 NBA season, precededByMerger, BAA–NBL merger of 1949]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precededByMerger Context triple: [1950–51 NBA season, precededByMerger, BAA–NBL merger of 1949]
-
A.
hasOwnerBeforeMerger
Indicates that an entity had a particular owner prior to a merger event taking place.
-
B.
hasMerger
Indicates a relationship where two or more entities combine into a single entity through a merger event.
-
C.
laterMergedWith
Indicates that one entity was combined into and became part of another entity at a subsequent point in time.
-
D.
regionBeforeMerger
Indicates that a region existed in its original form prior to being merged into a new or larger administrative or geographic entity.
-
E.
playedBeforeMerger
Indicates that one entity participated in or engaged in play prior to a specified merger event involving the other entity.
- 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_69e0b4be702c8190a3d2410a881d310a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6af1d0be481909e090193dcfd9cf6 |
completed | April 20, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 11:43 a.m.