Triple
T33206718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cincinnati Swords |
E850030
|
entity |
| Predicate | successorLeagueOfCityTeam |
P123268
|
FINISHED |
| Object | World Hockey Association |
—
|
NE NERFINISHED |
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: World Hockey Association | Statement: [Cincinnati Swords, successorLeagueOfCityTeam, World Hockey Association]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorLeagueOfCityTeam Context triple: [Cincinnati Swords, successorLeagueOfCityTeam, World Hockey Association]
-
A.
successorTeamInCity
Indicates that one team is the direct replacement or continuation of another team within the same city.
-
B.
successorLeagueClub
Indicates that one sports club is the direct successor or continuation of another club within the same league structure.
-
C.
successorClubPlaysIn
chosen
Indicates that the club which succeeds another club participates in a specified league or competition.
-
D.
successorClubName
Indicates the name of the club that directly succeeds or replaces another club in continuity or lineage.
-
E.
successorTeamLeague
Indicates that one sports league is the direct successor to another for a given team’s participation or affiliation.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff7fc835f08190afd1f8129b7a62a2 |
completed | May 9, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69ff7f2e99ac8190ba372a1358a05a30 |
completed | May 9, 2026, 6:38 p.m. |
Created at: May 1, 2026, 1:30 a.m.