Triple
T28833374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elaeum |
E728110
|
entity |
| Predicate | locatedNearAncientTown |
P55312
|
FINISHED |
| Object | Phigaleia |
—
|
NE NERFINISHED |
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: Phigaleia | Statement: [Elaeum, locatedNearAncientTown, Phigaleia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedNearAncientTown Context triple: [Elaeum, locatedNearAncientTown, Phigaleia]
-
A.
locatedInAncientCity
Indicates that an entity is situated within the boundaries or domain of an ancient city.
-
B.
locatedInOrNearModernSettlement
Indicates that something is situated within or in close proximity to a present-day town, city, or other populated settlement.
-
C.
nearAncientRegion
Indicates that one entity is located close to, or in the immediate vicinity of, a specified ancient geographical region.
-
D.
hasNearbyAncientCity
chosen
Indicates that one entity is located close to another entity that is classified as an ancient city.
-
E.
nearbyRomanTown
Indicates that one location is geographically close to a town that existed during the Roman period.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69ffb97b8ff8819088b105d99a0820c9 |
completed | May 9, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69ffb88ef7388190a710120ed76edc0e |
completed | May 9, 2026, 10:43 p.m. |
Created at: April 28, 2026, 6:38 a.m.