Triple
T30371566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chitrakoot Dham |
E772561
|
entity |
| Predicate | notableGhat |
P13904
|
FINISHED |
| Object | Ramghat |
E1068907
|
NE 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: Ramghat | Statement: [Chitrakoot Dham, notableGhat, Ramghat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGhat Context triple: [Chitrakoot Dham, notableGhat, Ramghat]
-
A.
hasPilgrimageGhatsIn
Indicates that a place possesses or contains pilgrimage ghats located within the specified area or region.
-
B.
hasGhat
chosen
Indicates that a place or location possesses or is associated with a ghat (a series of steps or landing area leading to a body of water).
-
C.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
D.
notableInCity
Indicates that an entity is particularly prominent, recognized, or significant within a specific city.
-
E.
riverGhat
Indicates a relationship where a location serves as a river ghat, i.e., a stepped or designated access point to a river used for activities such as bathing, rituals, or boarding boats.
- F. None of above.
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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a278942c478819093783bf7375031e6 |
completed | June 9, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 7:59 p.m.