Triple
T30793446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of Saint Nicholas in Myra |
E784162
|
entity |
| Predicate | hasSarcophagusOf |
P116513
|
FINISHED |
| Object | Saint Nicholas of Myra |
—
|
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: Saint Nicholas of Myra | Statement: [Church of Saint Nicholas in Myra, hasSarcophagusOf, Saint Nicholas of Myra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSarcophagusOf Context triple: [Church of Saint Nicholas in Myra, hasSarcophagusOf, Saint Nicholas of Myra]
-
A.
containsSarcophagusOf
chosen
Indicates that one entity physically houses or encloses the sarcophagus belonging to another entity.
-
B.
sarcophagusName
Indicates that a specific name is assigned to or associated with a sarcophagus.
-
C.
hasSarcophagusMaterial
Indicates that a sarcophagus is made from, or primarily composed of, a specified material.
-
D.
hasBurialChamberFor
Indicates that something (such as a structure or site) contains or is designated as a burial chamber intended for a particular individual or group.
-
E.
hasPartInGrave
Indicates that an entity includes another entity as a physical component or element within a grave.
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 29, 2026, 8:42 p.m.