Triple
T34805758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chir Ghat |
E1003349
|
entity |
| Predicate | hasSacredRiverBank |
P185987
|
FINISHED |
| Object | Yamuna 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: Yamuna River | Statement: [Chir Ghat, hasSacredRiverBank, Yamuna River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSacredRiverBank Context triple: [Chir Ghat, hasSacredRiverBank, Yamuna River]
-
A.
sacredRiver
Indicates that a river is regarded as holy or spiritually significant within a religious or cultural tradition.
-
B.
hasSacredSpring
Indicates that one entity possesses, contains, or is associated with a spring regarded as sacred or holy.
-
C.
hasSacredBridge
Indicates that one entity possesses or is associated with a bridge regarded as sacred or holy in relation to another entity.
-
D.
hasMythicalRiverConfluence
Indicates a relationship where a mythical or legendary river is believed to merge or join with another river or body of water.
-
E.
hasSacredPrecinct
Indicates that an entity possesses or contains a designated sacred area or precinct associated with religious or ritual significance.
- 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_69f76db600b88190989abdf08fce3b27 |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 3:59 p.m.