Triple
T35030872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tamaran |
E1010475
|
entity |
| Predicate | religionAndBeliefs |
P24121
|
FINISHED |
| Object | sun-related spiritual traditions |
—
|
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: sun-related spiritual traditions | Statement: [Tamaran, religionAndBeliefs, sun-related spiritual traditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: religionAndBeliefs Context triple: [Tamaran, religionAndBeliefs, sun-related spiritual traditions]
-
A.
religionOrBelief
Indicates that one entity holds, practices, or is associated with a particular religion, faith, or belief system.
-
B.
associatedReligionOrBelief
Indicates that an entity is connected to, identified with, or characterized by a particular religion or belief system.
-
C.
religiousTraditions
chosen
Indicates a relationship where certain religious customs, practices, or belief systems are associated with or observed by an entity.
-
D.
religionCommon
Indicates that the related entities share the same religion or religious affiliation.
-
E.
religiousSpectrum
Indicates a relationship that places entities along a range or continuum of religious belief, practice, or affiliation.
- 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff97637ad881908c24fe2cc6b036db |
completed | May 9, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69ff96c43a808190942eeda1934602db |
completed | May 9, 2026, 8:19 p.m. |
Created at: May 3, 2026, 4:01 p.m.