Triple
T24527073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IIHF European Cup |
E606696
|
entity |
| Predicate | organizingFederationHeadquarters |
P129113
|
FINISHED |
| Object | Zurich |
—
|
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: Zurich | Statement: [IIHF European Cup, organizingFederationHeadquarters, Zurich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizingFederationHeadquarters Context triple: [IIHF European Cup, organizingFederationHeadquarters, Zurich]
-
A.
organizingConfederationHeadquarters
Indicates that an entity serves as the headquarters location for the organizing confederation.
-
B.
organizerHeadquartersLocation
Indicates the place where the main offices or central administrative base of the organizing entity are located.
-
C.
subConfederationHeadquarters
Indicates the location where the administrative or governing headquarters of a sub-confederation is situated.
-
D.
headquartersAt
chosen
Indicates that an organization’s main administrative center or primary office is located at a specified place.
-
E.
organisingConfederation
Indicates that one entity serves as the organizing or governing confederation responsible for arranging, overseeing, or coordinating another entity or event.
- 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_69e2c4c85778819085f5da9af3569ad5 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:25 a.m.