Triple
T29510517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ναός του Ηφαίστου |
E748634
|
entity |
| Predicate | distanceFromAcropolis |
P202558
|
FINISHED |
| Object | μικρή απόσταση βορειοδυτικά της Ακρόπολης Αθηνών |
—
|
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: μικρή απόσταση βορειοδυτικά της Ακρόπολης Αθηνών | Statement: [Ναός του Ηφαίστου, distanceFromAcropolis, μικρή απόσταση βορειοδυτικά της Ακρόπολης Αθηνών]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromAcropolis Context triple: [Ναός του Ηφαίστου, distanceFromAcropolis, μικρή απόσταση βορειοδυτικά της Ακρόπολης Αθηνών]
-
A.
distanceToAthensCenter
Indicates the spatial distance between a given location and the center of Athens.
-
B.
distanceToEleusisApprox
Indicates that one entity has an approximate measured or estimated distance to the location Eleusis.
-
C.
distanceToTempleOfAphaia
Indicates the spatial distance between an entity and the Temple of Aphaia.
-
D.
distanceToApollonia
Indicates the measured spatial distance between a given entity and the location referred to as Apollonia.
-
E.
positionOnAcropolis
Indicates that something is located on or occupies a position on the Acropolis.
- 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_69f0bd461c208190bec20bbf24e02cc5 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_6a0091ad8b8c8190b0f00a3358e59bc1 |
completed | May 10, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_6a008f2813ec81909a54c2dfa5c75dc7 |
completed | May 10, 2026, 1:59 p.m. |
| PDg | Predicate description generation | batch_6a0091ac9ff08190b635eac6aa3f6128 |
completed | May 10, 2026, 2:09 p.m. |
Created at: April 28, 2026, 4:32 p.m.