Triple
T27169208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kundadri |
E682857
|
entity |
| Predicate | nearestGhatSection |
P46028
|
FINISHED |
| Object | Agumbe Ghat |
—
|
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: Agumbe Ghat | Statement: [Kundadri, nearestGhatSection, Agumbe Ghat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestGhatSection Context triple: [Kundadri, nearestGhatSection, Agumbe Ghat]
-
A.
nearbyGhats
chosen
Indicates that one location is situated close to or in the immediate vicinity of a ghat (such as a riverfront or stepped embankment).
-
B.
locatedOnGhatSection
Indicates that something is situated on or along a ghat section, typically a steeply graded or stepped riverbank or hillside area.
-
C.
hasPilgrimageGhatsIn
Indicates that a place possesses or contains pilgrimage ghats located within the specified area or region.
-
D.
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.
-
E.
closestLighthouse
Indicates that one lighthouse is the nearest in distance to a given reference point or entity compared to all other lighthouses.
- 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_69eefacf6e788190a75a64399d9e3109 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 9:22 a.m.