Triple
T24357445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Hornets |
E613961
|
entity |
| Predicate | mergedOrFoldedWithLeague |
P38582
|
FINISHED |
| Object | AAFC–NFL merger context |
—
|
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: AAFC–NFL merger context | Statement: [Chicago Hornets, mergedOrFoldedWithLeague, AAFC–NFL merger context]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mergedOrFoldedWithLeague Context triple: [Chicago Hornets, mergedOrFoldedWithLeague, AAFC–NFL merger context]
-
A.
mergedLeague
chosen
Indicates that two or more sports or competitive leagues have combined into a single unified league.
-
B.
originalLeagueFolded
Indicates that the sports league in which an entity originally competed has ceased operations or been disbanded.
-
C.
foldedInLeague
Indicates that a sports team or organization has ceased operations and been absorbed or discontinued within a particular league.
-
D.
leagueFolded
Indicates that a sports league has ceased operations and no longer exists as an active organization.
-
E.
includesLeague
Indicates that an entity (such as a competition, organization, or system) contains or encompasses a specific league as one of its components.
- 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_69e2d7dfe7f08190b7a1f3a36483ab05 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29349ee188190a9d54b2c725b8a27 |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287bb1b2c81909c2e7fcc392ad143 |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2 a.m.