Triple
T37568975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | babalorixá |
E934636
|
entity |
| Predicate | religiousBuildingLed |
P52882
|
FINISHED |
| Object | terreiro |
—
|
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: terreiro | Statement: [babalorixá, religiousBuildingLed, terreiro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousBuildingLed Context triple: [babalorixá, religiousBuildingLed, terreiro]
-
A.
churchBodyLed
Indicates that a church body is under the leadership, guidance, or authority of a specified leader or governing entity.
-
B.
religiousBuildingDedicatedTo
Indicates that a religious building is formally dedicated or consecrated to a particular deity, figure, or religious concept.
-
C.
isMajorReligiousBuildingOf
Indicates that a building serves as the primary or most significant religious structure associated with a particular religious group, institution, or area.
-
D.
religiousBuildingManaged
chosen
Indicates that one entity is responsible for overseeing, operating, or administering a religious building associated with another entity.
-
E.
religiousBuildingInstanceOf
Indicates that a specific religious building is an instance of a particular class or type of religious building.
- 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_69f76ecd99148190be327e391a70f5b6 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a002962f6e081909906d6436bae6407 |
completed | May 10, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_6a00284c9c7c8190a77f18a41eee55df |
completed | May 10, 2026, 6:40 a.m. |
Created at: May 3, 2026, 4:17 p.m.