Triple
T8698538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alodia |
E206462
|
entity |
| Predicate | religiousArchitectureType |
P34373
|
FINISHED |
| Object | churches |
—
|
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: churches | Statement: [Alodia, religiousArchitectureType, churches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousArchitectureType Context triple: [Alodia, religiousArchitectureType, churches]
-
A.
religiousSiteType
chosen
Indicates the specific kind or category of religious site associated with an entity (e.g., church, mosque, temple).
-
B.
religiousBuildingDedicatedTo
Indicates that a religious building is formally dedicated or consecrated to a particular deity, figure, or religious concept.
-
C.
religiousBuildingDesigned
Indicates that one entity (typically an architect or designer) is responsible for designing a religious building associated with the other entity.
-
D.
religiousHouse
Indicates that an entity is a religious institution or building used for worship, residence, or activities of a religious community.
-
E.
religiousBuildingManaged
Indicates that one entity is responsible for overseeing, operating, or administering a religious building associated with 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc58af50408190a3b81100a759795e |
completed | March 31, 2026, 11:28 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:34 p.m.