Triple
T26505637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sochi 2014 Organizing Committee |
E669535
|
entity |
| Predicate | organizedEventInCountry |
P46341
|
FINISHED |
| Object | Russia |
—
|
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: Russia | Statement: [Sochi 2014 Organizing Committee, organizedEventInCountry, Russia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizedEventInCountry Context triple: [Sochi 2014 Organizing Committee, organizedEventInCountry, Russia]
-
A.
organisedEvent
Indicates that an entity planned, coordinated, and carried out an event.
-
B.
countryHostedEvent
chosen
Indicates that a specific country served as the host location for a particular event.
-
C.
associatedCityEvent
Indicates a relationship where a city is linked to, involved in, or serves as the location for a particular event.
-
D.
eventTypeOrganized
Indicates that an entity organized or arranged a specific type or category of event.
-
E.
eventManagement
Indicates the organization, coordination, and oversight of all activities and resources involved in planning and executing an 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 1:16 a.m.