Triple
T34160303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corinth |
E876259
|
entity |
| Predicate | distanceToAthens_km |
P107413
|
FINISHED |
| Object | approximately 78 |
—
|
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: approximately 78 | Statement: [Corinth, distanceToAthens_km, approximately 78]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToAthens_km Context triple: [Corinth, distanceToAthens_km, approximately 78]
-
A.
distanceFromAthens_km
chosen
Indicates the physical distance, measured in kilometers, between a given place and the city of Athens.
-
B.
distanceFromAthensAirport
Indicates the spatial distance between a given location and Athens Airport.
-
C.
distanceToAthensCenter
Indicates the spatial distance between a given location and the center of Athens.
-
D.
distanceToPiraeus
Indicates the spatial distance between a given location or object and Piraeus.
-
E.
locatedDistanceFromAgrinio_km
Indicates the distance in kilometers between an entity’s location and the city of Agrinio.
- 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:54 a.m.