Triple
T37287593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archaeological Area of Agrigento |
E925575
|
entity |
| Predicate | originalAncientName |
P20952
|
FINISHED |
| Object | Akragas |
E55843
|
NE 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: Akragas | Statement: [Archaeological Area of Agrigento, originalAncientName, Akragas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalAncientName Context triple: [Archaeological Area of Agrigento, originalAncientName, Akragas]
-
A.
ancientNameOf
chosen
Indicates that one entity is the historical or ancient name by which the other entity was formerly known.
-
B.
ancientNameUnknown
Indicates that the ancient or original name associated with an entity is not known or cannot be determined.
-
C.
hasAncientEthnicName
Indicates that an entity is associated with an ethnic name or designation that originates from ancient times.
-
D.
ancientNameMeaning
Indicates that an entity’s ancient or historical name carries a particular meaning or interpretation.
-
E.
ancientNameOfServedSettlement
Indicates that the object is an earlier or historical name by which the settlement served by the subject was known.
- F. None of above.
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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40e060b22481908709966b58646b0e |
completed | June 28, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.