Triple
T25222457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thai architecture |
E631999
|
entity |
| Predicate | alsoReflectsReligion |
P29112
|
FINISHED |
| Object | 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: animist beliefs | Statement: [Thai architecture, alsoReflectsReligion, animist beliefs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alsoReflectsReligion Context triple: [Thai architecture, alsoReflectsReligion, animist beliefs]
-
A.
hasReligious
Indicates that an entity is associated with, practices, or adheres to a particular religion or religious affiliation.
-
B.
associatedReligionOrBelief
Indicates that an entity is connected to, identified with, or characterized by a particular religion or belief system.
-
C.
religionOrBelief
Indicates that one entity holds, practices, or is associated with a particular religion, faith, or belief system.
-
D.
influencedByReligion
chosen
Indicates that an entity’s characteristics, decisions, or development are shaped or affected by religious beliefs, practices, or institutions.
-
E.
religiousAffiliation
Indicates that one entity has a specified religious association, belief system, or denominational membership.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47cc0578881909ed1e40c09fdc38d |
completed | May 1, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:03 p.m.