Triple
T14015556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Games of the V Olympiad |
E337194
|
entity |
| Predicate | hostCityLongitude |
P112471
|
FINISHED |
| Object | 18.0686 E |
—
|
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: 18.0686 E | Statement: [Games of the V Olympiad, hostCityLongitude, 18.0686 E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostCityLongitude Context triple: [Games of the V Olympiad, hostCityLongitude, 18.0686 E]
-
A.
homeCityLatitude
Indicates the geographic latitude coordinate associated with an entity’s home city.
-
B.
typicalCityLongitude
Indicates the standard or representative longitude value associated with a given city.
-
C.
landingSiteLongitude
Indicates the longitudinal coordinate (east–west position) of a specified landing site on a planetary body.
-
D.
hostCityRegion
Indicates the city or broader region that serves as the host location for a specified event or entity.
-
E.
typicalCityLatitude
Indicates the usual or representative latitude at which a given city is located.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2f396b648190927e5718c3bb6511 |
completed | April 14, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69de05a802ac819090604025aae6a4d5 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239524688190a0f2408c239cfcaa |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 9, 2026, 10:19 p.m.