Triple
T38263276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WHA 1978–79 season |
E1017983
|
entity |
| Predicate | locationOfLeagueOffices |
P18007
|
FINISHED |
| Object | North America |
E335
|
NE 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: North America | Statement: [WHA 1978–79 season, locationOfLeagueOffices, North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfLeagueOffices Context triple: [WHA 1978–79 season, locationOfLeagueOffices, North America]
-
A.
locationOfLeague
Indicates the place or geographic area where a sports league is based, hosted, or primarily operates.
-
B.
locationOfLeagueHeadquarters
chosen
Indicates the place where a league’s main administrative headquarters is situated.
-
C.
locationLeague
Indicates that an entity (such as a sports team or club) is associated with or participates in a particular league.
-
D.
hostLeagueOffice
Indicates that an entity serves as the location or venue where a league’s official administrative office is situated.
-
E.
stateLeagueLocation
Indicates the geographic location (such as city or venue) where a particular state-level league is based or takes place.
- F. None of above.
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_69f76de33e4481909099fa812709bd42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a419df294c88190bcc4a9a869d7c68f |
completed | June 28, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.