Triple
T31997041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Church of Our Lady Mary of Zion |
E817018
|
entity |
| Predicate | accessToSanctuary |
P135442
|
FINISHED |
| Object | restricted |
—
|
LITERAL 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: restricted | Statement: [Church of Our Lady Mary of Zion, accessToSanctuary, restricted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessToSanctuary Context triple: [Church of Our Lady Mary of Zion, accessToSanctuary, restricted]
-
A.
accessToInnerSanctum
Indicates that an entity is permitted to enter or use a restricted, highly exclusive inner area or domain.
-
B.
guardedEntranceTo
Indicates that one entity serves as a protective or controlling barrier for access to another entity’s entrance.
-
C.
hadSanctuaryOf
Indicates that an entity possessed or hosted a sanctuary dedicated to another entity.
-
D.
accessMission
Indicates that an entity is permitted to enter, use, or interact with a specific mission or mission-related resources.
-
E.
templeAccess
chosen
Indicates that an entity has permission or the ability to enter or use a particular temple or temple-related area.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: May 1, 2026, 12:14 a.m.