Triple
T4332517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uatsdin |
E97385
|
entity |
| Predicate | hasRitualPlace |
P27744
|
FINISHED |
| Object | holy grove |
—
|
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: holy grove | Statement: [Uatsdin, hasRitualPlace, holy grove]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRitualPlace Context triple: [Uatsdin, hasRitualPlace, holy grove]
-
A.
hasRitualSpace
chosen
Indicates that an entity possesses or is associated with a designated space used for ritual or ceremonial activities.
-
B.
hasRitual
Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
-
C.
hasAltar
Indicates that one entity possesses, contains, or includes an altar as part of its features or components.
-
D.
hasRitualObject
Indicates that an entity possesses, uses, or is associated with an object specifically employed in a ritual or ceremonial context.
-
E.
hasShrinesIn
Indicates that one entity possesses or maintains shrines that are located within the area or domain of 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_69b3454662a481908fbcd0bbfaa3a0a4 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3514faaac819081475681fd10da24 |
completed | March 12, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69b34f4e13fc8190a42c519f37959d27 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:13 p.m.