Triple
T37333025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 FIS Alpine World Ski Championships |
E926803
|
entity |
| Predicate | womenEventsVenue |
P187739
|
FINISHED |
| Object | Planai |
—
|
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: Planai | Statement: [2013 FIS Alpine World Ski Championships, womenEventsVenue, Planai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: womenEventsVenue Context triple: [2013 FIS Alpine World Ski Championships, womenEventsVenue, Planai]
-
A.
eventsForWomen
Indicates that the associated events are intended for, targeted at, or specifically involve women.
-
B.
hostedEventsNearby
Indicates that an entity has organized or is responsible for events occurring within a nearby geographic area relative to another reference point.
-
C.
organisedEvent
Indicates that an entity planned, coordinated, and carried out an event.
-
D.
eventManagement
Indicates the organization, coordination, and oversight of all activities and resources involved in planning and executing an event.
-
E.
individualEvents
Indicates that the subject is associated with one or more distinct, separately identifiable events rather than a single aggregated or continuous occurrence.
- F. None of above. chosen
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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
| PDg | Predicate description generation | batch_69fb8c37931c81909da038c18ed9add2 |
completed | May 6, 2026, 6:45 p.m. |
Created at: May 3, 2026, 4:16 p.m.