Triple
T29429965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pilgrimage to Hierapolis |
E746400
|
entity |
| Predicate | centeredOnSanctuary |
P134284
|
FINISHED |
| Object | sanctuary of Atargatis at Hierapolis |
—
|
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: sanctuary of Atargatis at Hierapolis | Statement: [pilgrimage to Hierapolis, centeredOnSanctuary, sanctuary of Atargatis at Hierapolis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centeredOnSanctuary Context triple: [pilgrimage to Hierapolis, centeredOnSanctuary, sanctuary of Atargatis at Hierapolis]
-
A.
viewOnSanctuary
Indicates that an entity holds a particular perspective, opinion, or stance regarding a sanctuary or sanctuary-related concept.
-
B.
locationInSanctuary
Indicates that an entity is located within the boundaries of a designated sanctuary area.
-
C.
governedSanctuary
Indicates that an entity holds governing authority or administrative control over a sanctuary.
-
D.
isLinkedToSanctuary
chosen
Indicates that an entity has a connection or association with a sanctuary, such as being related, directed, or assigned to it.
-
E.
hadSanctuaryOf
Indicates that an entity possessed or hosted a sanctuary dedicated 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_69f0a7a06e0081908add494075912eb4 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66ac8bb9081908af9b31ab052956d |
completed | May 2, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:12 p.m.