Triple
T30211497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | cult of Artemis |
E768077
|
entity |
| Predicate | hasMajorSanctuaryAt |
P5445
|
FINISHED |
| Object | Ephesus |
—
|
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: Ephesus | Statement: [cult of Artemis, hasMajorSanctuaryAt, Ephesus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorSanctuaryAt Context triple: [cult of Artemis, hasMajorSanctuaryAt, Ephesus]
-
A.
hasMajorSanctuary
chosen
Indicates that an entity possesses or is associated with a primary or principal sanctuary location.
-
B.
situatedInProtectedArea
Indicates that an entity is located within the boundaries of a designated protected area (such as a reserve, park, or conservation zone).
-
C.
countryProtectedAreaSystem
Indicates that a country has an established system or network of designated protected areas under its jurisdiction.
-
D.
modernProtectedArea
Indicates that an area is designated and managed as a contemporary legally recognized protected area under modern conservation frameworks.
-
E.
hasUNESCOBiosphereReserve
Indicates that an entity includes, contains, or is associated with a designated UNESCO Biosphere Reserve.
- 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_69ff9361943c81909544203cbc998a69 |
completed | May 9, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69ff913138a08190b59bdc9d8d199eb3 |
completed | May 9, 2026, 7:55 p.m. |
Created at: April 29, 2026, 7:32 p.m.