Triple
T30211292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanctuary of Athena Alea |
E768072
|
entity |
| Predicate | wasMajorCultCenterOf |
P21627
|
FINISHED |
| Object | Athena in Arcadia |
—
|
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: Athena in Arcadia | Statement: [Sanctuary of Athena Alea, wasMajorCultCenterOf, Athena in Arcadia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasMajorCultCenterOf Context triple: [Sanctuary of Athena Alea, wasMajorCultCenterOf, Athena in Arcadia]
-
A.
cultSite
chosen
Indicates a location that is or was used for religious or ritual worship activities.
-
B.
hasArchaeologicalSitesFrom
Indicates that an entity contains or is associated with archaeological sites dating from a specified time period or era.
-
C.
hasArchaeologicalSiteIn
Indicates that an entity possesses, contains, or is associated with an archaeological site located within a specified place or region.
-
D.
hasCultPlaceType
Indicates that an entity is associated with a place used for cultic or religious activities of a specified type.
-
E.
culturalSite
Indicates that one entity is recognized or designated as a cultural site associated with or located in relation to another entity.
- 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_69f2247eb0848190b4032f302d39c0d9 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ff185488190a49b208e4ac6cf59 |
completed | May 2, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:32 p.m.