Triple
T13223615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanctuary of Demeter at Megara |
E314817
|
entity |
| Predicate | region |
P40
|
FINISHED |
| Object | Megaris |
E314813
|
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: Megaris | Statement: [Sanctuary of Demeter at Megara, region, Megaris]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Megaris Context triple: [Sanctuary of Demeter at Megara, region, Megaris]
-
A.
Megaris
chosen
Megaris was an ancient Greek region in central Greece, situated between Attica and Corinthia and centered around the city-state of Megara.
-
B.
Erasinos
Erasinos is an ancient river in the region of Attica, Greece, historically associated with the sanctuary and coastal area of Brauron.
-
C.
Damaskinos
Damaskinos is a Greek-origin surname historically associated with notable religious and cultural figures.
-
D.
Ergamenes
Ergamenes was a king of the ancient Kingdom of Kush, known for asserting royal authority over the priesthood and initiating significant cultural and political reforms.
-
E.
Gorgidas
Gorgidas was an ancient Theban military leader best known for organizing and commanding the elite Sacred Band of Thebes.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf74d708190a61d8ad938653b06 |
completed | April 10, 2026, 11:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6ff24be9881908b96f3e72325e55f |
completed | May 3, 2026, 7:54 a.m. |
Created at: April 9, 2026, 9:19 p.m.