Triple
T20598240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pirita River |
E506105
|
entity |
| Predicate | wasVenueAreaFor |
P112843
|
FINISHED |
| Object | 1980 Summer Olympics sailing events vicinity |
—
|
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: 1980 Summer Olympics sailing events vicinity | Statement: [Pirita River, wasVenueAreaFor, 1980 Summer Olympics sailing events vicinity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasVenueAreaFor Context triple: [Pirita River, wasVenueAreaFor, 1980 Summer Olympics sailing events vicinity]
-
A.
hasVenueFor
chosen
Indicates that one entity provides or serves as the location or setting where an event, activity, or function takes place for another entity.
-
B.
hasVenueIn
Indicates that an event, activity, or occurrence takes place at a specific venue located within a particular geographic area or location.
-
C.
performedAtVenue
Indicates that an event or performance took place at a specific venue or location.
-
D.
previousVenue
Indicates that one venue was used or occupied before another in a sequence of venues.
-
E.
venueAlsoKnownAs
Indicates that a venue has an alternative name or alias by which it is also known.
- 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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa1e251c8190926dafe1402eb63c |
completed | April 20, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:40 a.m.