Triple
T37086309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tilakwada |
E918293
|
entity |
| Predicate | hasNearbyMajorProject |
P69562
|
FINISHED |
| Object | Sardar Sarovar Project (on Narmada 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: Sardar Sarovar Project (on Narmada River) | Statement: [Tilakwada, hasNearbyMajorProject, Sardar Sarovar Project (on Narmada River)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyMajorProject Context triple: [Tilakwada, hasNearbyMajorProject, Sardar Sarovar Project (on Narmada River)]
-
A.
hasNearbyProject
chosen
Indicates that one entity has a project located within a close or specified proximity to another entity or reference point.
-
B.
hasProject
Indicates that an entity is associated with or responsible for a particular project.
-
C.
hasLongRunningProject
Indicates that an entity is engaged in or responsible for a project that extends over a long duration of time.
-
D.
hasPlannedProjects
Indicates that an entity is associated with projects that are intended or scheduled to be carried out in the future.
-
E.
hasProjectIn
Indicates that an entity is involved with or associated with a project that takes place within a specified location or context.
- 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_69f76e9952b88190a6fe01ba01476520 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a008098e5dc8190b7ccad8bab780343 |
completed | May 10, 2026, 12:56 p.m. |
| PD | Predicate disambiguation | batch_6a008037267c8190990225a6ff0b3694 |
completed | May 10, 2026, 12:55 p.m. |
Created at: May 3, 2026, 4:14 p.m.