Triple
T9738701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adena culture |
E236130
|
entity |
| Predicate | hasReligionOrBelief |
P56366
|
FINISHED |
| Object | ancestor veneration |
—
|
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 veneration | Statement: [Adena culture, hasReligionOrBelief, ancestor veneration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligionOrBelief Context triple: [Adena culture, hasReligionOrBelief, ancestor veneration]
-
A.
religionOrBelief
chosen
Indicates that one entity holds, practices, or is associated with a particular religion, faith, or belief system.
-
B.
hasAssociatedReligion
Indicates that an entity is connected with or linked to a particular religion.
-
C.
hasReligiousSee
Indicates that one entity serves as the ecclesiastical or religious jurisdiction/seat (see) of another entity.
-
D.
declaredReligion
Indicates that an entity has formally stated or reported a particular religious affiliation.
-
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_69ca84d313e88190983ee6ffd0ef60d2 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9ef43fec8190987628f401a27436 |
completed | April 1, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69cd03c6ffc88190a5e9569e19122ad5 |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:22 p.m.