Triple
T33314851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assi Nala |
E852986
|
entity |
| Predicate | associatedWithGhat |
P13904
|
FINISHED |
| Object | Assi Ghat |
E133278
|
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: Assi Ghat | Statement: [Assi Nala, associatedWithGhat, Assi Ghat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithGhat Context triple: [Assi Nala, associatedWithGhat, Assi Ghat]
-
A.
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).
-
B.
associatedWithGharana
Indicates a relationship where an entity is linked or connected to a particular gharana (a specific musical or artistic lineage or school).
-
C.
hasGhatCount
Indicates the number of ghats associated with a given entity.
-
D.
locatedOnGhatSection
Indicates that something is situated on or along a ghat section, typically a steeply graded or stepped riverbank or hillside area.
-
E.
associatedWithRitu
Indicates a relationship in which an entity has some form of connection, link, or involvement with Ritu, without specifying the exact nature of that association.
- 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_69f349679fd8819093b9b40e989440e3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3551faa46081908d212f747f408c1e |
completed | June 19, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:33 a.m.