Triple
T29373720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Artemis at Sardis |
E744928
|
entity |
| Predicate | partOfSanctuaryOf |
P134284
|
FINISHED |
| Object | Artemis at Sardis |
—
|
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: Artemis at Sardis | Statement: [Temple of Artemis at Sardis, partOfSanctuaryOf, Artemis at Sardis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfSanctuaryOf Context triple: [Temple of Artemis at Sardis, partOfSanctuaryOf, Artemis at Sardis]
-
A.
situatedInProtectedArea
Indicates that an entity is located within the boundaries of a designated protected area (such as a reserve, park, or conservation zone).
-
B.
isLinkedToSanctuary
chosen
Indicates that an entity has a connection or association with a sanctuary, such as being related, directed, or assigned to it.
-
C.
hadSanctuaryOf
Indicates that an entity possessed or hosted a sanctuary dedicated to another entity.
-
D.
hasMajorSanctuary
Indicates that an entity possesses or is associated with a primary or principal sanctuary location.
-
E.
partOfProtectedAreaCategory
Indicates that one protected area belongs to, or is classified under, a specific protected area category.
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69fe96c2647c819082989f11e1ae3d35 |
completed | May 9, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69fe928615448190af939e5a94be55bb |
completed | May 9, 2026, 1:48 a.m. |
Created at: April 28, 2026, 2:29 p.m.