Triple
T25814712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mountain of Light |
E650216
|
entity |
| Predicate | hasTypeOfReverence |
P5315
|
FINISHED |
| Object | venerated as site of first revelation |
—
|
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: venerated as site of first revelation | Statement: [Mountain of Light, hasTypeOfReverence, venerated as site of first revelation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfReverence Context triple: [Mountain of Light, hasTypeOfReverence, venerated as site of first revelation]
-
A.
venerationType
chosen
Indicates the specific manner or category of reverence or worship directed toward an entity.
-
B.
hasHonorificType
Indicates that an entity is associated with a specific type or category of honorific title or form of address.
-
C.
isWorshippedFor
Indicates that one entity is revered or honored by another specifically because of a particular quality, deed, or attribute.
-
D.
hasDevoteeType
Indicates that an entity has a devotee characterized by a specific type or category of devotion.
-
E.
hasHonorificBasis
Indicates that one entity serves as the basis or justification for assigning an honorific title or respectful form of address to another entity.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 22, 2026, 7:25 a.m.