Triple
T30215113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Songsarek |
E768181
|
entity |
| Predicate | traditionalReligionOf |
P56366
|
FINISHED |
| Object | Garo people |
—
|
NE NERFINISHED |
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: Garo people | Statement: [Songsarek, traditionalReligionOf, Garo people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalReligionOf Context triple: [Songsarek, traditionalReligionOf, Garo people]
-
A.
traditionalReligionName
Indicates that an entity has a name specifically associated with a traditional or indigenous religion.
-
B.
religiousTraditions
Indicates a relationship where certain religious customs, practices, or belief systems are associated with or observed by an entity.
-
C.
officialReligion
Indicates that a particular religion is formally recognized and designated as the official or state religion of an entity (such as a country or region).
-
D.
traditionalReligionHighGod
Indicates that within a traditional religion, the entity functions as a supreme or highest deity (high god) in that belief system.
-
E.
religionOrBelief
chosen
Indicates that one entity holds, practices, or is associated with a particular religion, faith, or belief system.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fda94697c4819081291967202248be |
completed | May 8, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_69fda5973fcc8190a57daef31fb70a49 |
completed | May 8, 2026, 8:57 a.m. |
Created at: April 29, 2026, 7:33 p.m.