Triple
T26795639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ngada indigenous religion |
E670939
|
entity |
| Predicate | usesSacredSpaceType |
P101233
|
FINISHED |
| Object | village ritual plaza |
—
|
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: village ritual plaza | Statement: [Ngada indigenous religion, usesSacredSpaceType, village ritual plaza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSacredSpaceType Context triple: [Ngada indigenous religion, usesSacredSpaceType, village ritual plaza]
-
A.
usesSacredSpace
chosen
Indicates that an entity makes use of a designated sacred or holy space for its activities or purposes.
-
B.
isInUseForWorship
Indicates that something is currently being used for religious or worship-related activities.
-
C.
sacredTo
Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
-
D.
sacramentalUseOf
Indicates the use of something as a sacrament or within a sacramental religious rite or practice.
-
E.
usedSacredVesselsFrom
Indicates that one entity made use of sacred or consecrated vessels that originated from or belonged to 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_69eeb31fbd888190a82dac5822e453bc |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 4:19 a.m.