Triple
T29129893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agastya Lake |
E738342
|
entity |
| Predicate | consideredSacred |
P21134
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Agastya Lake, consideredSacred, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consideredSacred Context triple: [Agastya Lake, consideredSacred, true]
-
A.
sacredTo
Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
-
B.
sacredStatus
chosen
Indicates that something holds a revered, holy, or religiously significant status within a particular belief system or tradition.
-
C.
sacredToCommunity
Indicates that something holds special religious or spiritual significance and is revered or protected by a particular community.
-
D.
sacredElement
Indicates that one entity is regarded as holy, revered, or spiritually significant within the religious or cultural context of the other entity.
-
E.
sacredDirection
Indicates a directional relationship that is regarded as holy, spiritually significant, or ritually privileged within a religious or cultural context.
- 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_69f07cb29cdc8190afa55444553de60c |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 11:31 a.m.