Triple
T29616391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hindus |
E754874
|
entity |
| Predicate | sacredGeographyIncludes |
P149603
|
FINISHED |
| Object | Ganges River |
—
|
NE NERFINISHED |
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: Ganges River | Statement: [Hindus, sacredGeographyIncludes, Ganges River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sacredGeographyIncludes Context triple: [Hindus, sacredGeographyIncludes, Ganges River]
-
A.
sacredHill
Indicates that a hill holds religious or spiritual significance within a belief system or tradition.
-
B.
hasSpiritualSitesIn
chosen
Indicates that one entity possesses or contains spiritual or religious sites located within the boundaries of another entity.
-
C.
sacredTo
Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
-
D.
sacredDirection
Indicates a directional relationship that is regarded as holy, spiritually significant, or ritually privileged within a religious or cultural context.
-
E.
regionOfReligiousSignificance
Indicates that a location or area holds recognized religious importance, such as being sacred, holy, or central to religious practices or beliefs.
- 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_69f0ef85f62081909842b59fdf8717e1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66e2198f88190b384af5844ab9415 |
completed | May 2, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:31 p.m.