Triple
T6819054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Temple of Athena |
E156848
|
entity |
| Predicate | positionOnAcropolis |
P73243
|
FINISHED |
| Object | south of the later Erechtheion |
—
|
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: south of the later Erechtheion | Statement: [Old Temple of Athena, positionOnAcropolis, south of the later Erechtheion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnAcropolis Context triple: [Old Temple of Athena, positionOnAcropolis, south of the later Erechtheion]
-
A.
hasAcropolis
Indicates that one entity possesses, contains, or is associated with an acropolis (a fortified high area or citadel).
-
B.
positionOfStatue
Indicates the spatial location where a statue is situated or placed.
-
C.
ancientPolisCenter
Indicates that a location functioned as the central urban, political, or social hub of an ancient polis (city-state).
-
D.
rankOnMountAthos
Indicates the hierarchical or positional rank that an entity holds within the monastic or administrative structure on Mount Athos.
-
E.
pantheon
Indicates a relationship where a group of deities collectively belong to or are recognized within the same religious or mythological system.
- 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_69c688298a288190af3f285d57f76bbe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d35781e88190a45d1386706d4422 |
completed | March 27, 2026, 6:58 p.m. |
| PD | Predicate disambiguation | batch_69c6d09bb4f881909bf20c188cb3e8e1 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d1d5f1908190989efc8a2d18c965 |
completed | March 27, 2026, 6:52 p.m. |
Created at: March 27, 2026, 2:17 p.m.