Triple
T20085694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naga gem Nagamani |
E500121
|
entity |
| Predicate | domainOfBelief |
P138663
|
FINISHED |
| Object | faith-based 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: faith-based traditions | Statement: [Naga gem Nagamani, domainOfBelief, faith-based traditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domainOfBelief Context triple: [Naga gem Nagamani, domainOfBelief, faith-based traditions]
-
A.
regionOfBelief
Indicates a spatial or conceptual area within which a particular belief, assumption, or proposition is considered to hold true.
-
B.
originBelief
Indicates a belief or assumption about where something or someone comes from or originated.
-
C.
theologicalBelief
Indicates that one entity holds or endorses a specific religious or theological doctrine, view, or set of beliefs about the divine or spiritual matters.
-
D.
characterBelief
Indicates that one character holds a belief, opinion, or assumption about another entity, situation, or proposition.
-
E.
basedOnBelief
Indicates that one entity’s action, decision, or assertion is grounded in, motivated by, or derived from a particular belief held by that entity.
- F. None of above. chosen
Provenance (4 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6655ae9ec8190bde2f17452639de8 |
completed | April 20, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69e54cf369b88190931532420517dac7 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:41 p.m.