Triple
T4272428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pomo people |
E96968
|
entity |
| Predicate | currentReligion |
P52189
|
FINISHED |
| Object | traditional 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 beliefs | Statement: [Pomo people, currentReligion, traditional beliefs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentReligion Context triple: [Pomo people, currentReligion, traditional beliefs]
-
A.
laterReligion
Indicates that one religion or religious affiliation chronologically follows or replaces another for the same entity.
-
B.
subjectReligion
chosen
Indicates that the subject is associated with, practices, or adheres to a particular religion.
-
C.
religionCommon
Indicates that the related entities share the same religion or religious affiliation.
-
D.
contemporaryReligion
Indicates that two entities practice or are associated with religions that exist and are followed during the same historical time period.
-
E.
otherReligion
Indicates that one entity follows or is associated with a religion that is different from the religion of 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34ffce3d8819083d2278547fa52c1 |
completed | March 12, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69b347faa45481908c19c29fb906dc92 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.