Triple
T37671065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belarus and Latvia |
E937957
|
entity |
| Predicate | sportOfEventCoHosted |
P39565
|
FINISHED |
| Object | ice hockey |
—
|
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: ice hockey | Statement: [Belarus and Latvia, sportOfEventCoHosted, ice hockey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportOfEventCoHosted Context triple: [Belarus and Latvia, sportOfEventCoHosted, ice hockey]
-
A.
cohostedSportingEvents
chosen
Indicates that two or more entities jointly organized or hosted one or more sporting events together.
-
B.
sportsEventHosted
Indicates that a particular sports event was organized, arranged, or held by a specified host entity (such as a venue, organization, or city).
-
C.
sportingEventAssociatedWith
Indicates that there is a relevant connection or involvement between a sporting event and another entity (such as a person, team, organization, or place).
-
D.
sportEvent
Indicates a relationship where an entity is involved in, associated with, or characterizes a competitive or organized sporting event.
-
E.
hostsSport
Indicates that one entity provides the venue or location where a particular sport is played or conducted.
- 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_69f76ed7b1408190ba8c93c53cb8becf |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.