Triple
T34770895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | maqdas |
E1002358
|
entity |
| Predicate | roleInChurchBuilding |
P203025
|
FINISHED |
| Object | innermost chamber |
—
|
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: innermost chamber | Statement: [maqdas, roleInChurchBuilding, innermost chamber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInChurchBuilding Context triple: [maqdas, roleInChurchBuilding, innermost chamber]
-
A.
roleInChurchProcess
Indicates that an entity holds a specific role or function within a defined church-related process or procedure.
-
B.
positionInChurch
Indicates that one entity holds a specific role, office, or rank within a church organization or hierarchy.
-
C.
ecclesialRole
Indicates that one entity holds or is assigned a specific role, office, or function within a church or ecclesiastical structure in relation to another entity.
-
D.
ecclesiasticalRole
Indicates that one entity holds or is assigned a specific religious or church-related office, function, or position in relation to another entity.
-
E.
seatOfChurchLeadership
Indicates the location that serves as the central administrative or authoritative base for a church’s leadership.
- F. None of above. chosen
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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a0115fb84448190b8b67a5ace7b289a |
completed | May 10, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_6a0114ef60a081908f8db7868cf29b2f |
completed | May 10, 2026, 11:29 p.m. |
| PDg | Predicate description generation | batch_6a0115fadcec8190bd1be2b44c1fc397 |
completed | May 10, 2026, 11:34 p.m. |
Created at: May 3, 2026, 3:59 p.m.