Triple
T38270597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lung Yeuk Tau villages |
E1021195
|
entity |
| Predicate | religiousAndRitualPractices |
P24121
|
FINISHED |
| Object | ancestor worship |
—
|
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: ancestor worship | Statement: [Lung Yeuk Tau villages, religiousAndRitualPractices, ancestor worship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religiousAndRitualPractices Context triple: [Lung Yeuk Tau villages, religiousAndRitualPractices, ancestor worship]
-
A.
practicesReligion
Indicates that an entity actively follows, observes, or participates in the beliefs, rituals, and customs of a particular religion.
-
B.
religiousOrRitualAssociation
Indicates a connection between entities based on shared religious, spiritual, or ritual practices, roles, or significance.
-
C.
religiousTraditions
chosen
Indicates a relationship where certain religious customs, practices, or belief systems are associated with or observed by an entity.
-
D.
cultPractices
Indicates involvement in or performance of rituals, beliefs, or behaviors associated with a cult.
-
E.
religiousFunction
Indicates that one entity serves a religious role, purpose, or function in relation 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_69f76dee198c8190bf5109421e47a658 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a005247dba08190acadf962bcefe4a0 |
completed | May 10, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_6a00519029848190a234358dfba45084 |
completed | May 10, 2026, 9:36 a.m. |
Created at: May 3, 2026, 4:30 p.m.