Triple
T33141877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of Saint Theodore |
E848174
|
entity |
| Predicate | locatedInMonasticSettlement |
P20652
|
FINISHED |
| Object | Wadi El Natrun monastic complex |
E770517
|
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: Wadi El Natrun monastic complex | Statement: [Church of Saint Theodore, locatedInMonasticSettlement, Wadi El Natrun monastic complex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInMonasticSettlement Context triple: [Church of Saint Theodore, locatedInMonasticSettlement, Wadi El Natrun monastic complex]
-
A.
monasticResidence
Indicates that one entity serves as the place of residence for a monastic individual or community.
-
B.
containsMonastery
chosen
Indicates that one entity includes or encompasses a monastery within its boundaries or composition.
-
C.
stillInUseAsMonastery
Indicates that a building or site continues to function as a monastery in the present time.
-
D.
monastery
Indicates that an entity is or functions as a monastery, typically a religious community or building where monastics live and practice.
-
E.
monasteriesAre
Indicates that a subject is classified as, functions as, or is identified with monasteries.
- F. None of above.
Provenance (4 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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a036054129081909e66c5d62015e6c1 |
completed | May 12, 2026, 5:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a351624d52081909ac17df6d19d04f0 |
completed | June 19, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_6a035f17cbf88190acd6bdbfc9789ffb |
completed | May 12, 2026, 5:10 p.m. |
Created at: May 1, 2026, 1:28 a.m.