Triple
T25345116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orango |
E635522
|
entity |
| Predicate | hasReligionPractice |
P17769
|
FINISHED |
| Object | traditional animist beliefs |
—
|
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: traditional animist beliefs | Statement: [Orango, hasReligionPractice, traditional animist beliefs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligionPractice Context triple: [Orango, hasReligionPractice, traditional animist beliefs]
-
A.
hasReligiousObservance
Indicates that an entity practices, observes, or participates in a particular religious rite, ceremony, or tradition.
-
B.
practicesReligion
chosen
Indicates that an entity actively follows, observes, or participates in the beliefs, rituals, and customs of a particular religion.
-
C.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
D.
hasAssociatedReligion
Indicates that an entity is connected with or linked to a particular religion.
-
E.
isUsedByReligion
Indicates that something (such as an object, practice, text, or symbol) is employed or utilized within the context of a particular religion.
- 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_69e75a9ac5d881909387ed766e20cd47 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 21, 2026, 1:34 p.m.