Triple
T28541576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KHL on ESPN |
E722303
|
entity |
| Predicate | regionOfLeagueCovered |
P181400
|
FINISHED |
| Object | Eurasia |
—
|
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: Eurasia | Statement: [KHL on ESPN, regionOfLeagueCovered, Eurasia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionOfLeagueCovered Context triple: [KHL on ESPN, regionOfLeagueCovered, Eurasia]
-
A.
regionOfLeagueParticipation
chosen
Indicates the geographic region in which a league’s participation or competition takes place.
-
B.
regionLeague
Indicates a relationship where a specific region is associated with, belongs to, or is governed by a particular league or league-level organization.
-
C.
hasRegionalLeagues
Indicates that an entity organizes, oversees, or is associated with multiple leagues that operate at regional or subnational levels.
-
D.
primaryLeagueCovered
Indicates that a particular league is the main or principal league included within a given coverage or service.
-
E.
homeRegionLeague
Indicates that a league is the primary or native regional competition associated with an entity (such as a team or club).
- 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_69f01a5e42348190b1ffbca26e739c84 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: April 28, 2026, 3:35 a.m.