Triple
T3023780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Early Horizon |
E82527
|
entity |
| Predicate | hasReligionType |
P27703
|
FINISHED |
| Object | Andean religious tradition |
—
|
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: Andean religious tradition | Statement: [Early Horizon, hasReligionType, Andean religious tradition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligionType Context triple: [Early Horizon, hasReligionType, Andean religious tradition]
-
A.
hasAssociatedReligion
Indicates that an entity is connected with or linked to a particular religion.
-
B.
hasReligiousInstitutionType
Indicates that an entity is associated with, or classified by, a specific type of religious institution.
-
C.
hasReligiousCharacter
chosen
Indicates that an entity possesses a religious nature, function, or affiliation, or is characterized by religious aspects or significance.
-
D.
recognizesReligion
Indicates that one entity formally acknowledges or accepts another entity as a valid or legitimate religion.
-
E.
hasReligiousOrigin
Indicates that something originates from, is derived from, or is fundamentally based on a religious tradition, belief system, or practice.
- 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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9ab8e0a48190ac79e674abd181cf |
completed | March 8, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69ad961c430c8190ac48f2e3c7e7c649 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3 p.m.