Triple
T4816311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nathpa Jhakri Dam |
E107596
|
entity |
| Predicate | designedHead |
P59812
|
FINISHED |
| Object | ~428 m |
—
|
LITERAL 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: ~428 m | Statement: [Nathpa Jhakri Dam, designedHead, ~428 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedHead Context triple: [Nathpa Jhakri Dam, designedHead, ~428 m]
-
A.
headType
Indicates the specific kind or category of head associated with an entity (e.g., type of head part, head role, or head classification in a structure or system).
-
B.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
C.
designedWith
Indicates that one entity was created, planned, or developed using another entity as a tool, method, or guiding basis in its design process.
-
D.
headShape
Indicates the characteristic form or contour of an entity’s head.
-
E.
coHeads
Indicates that two or more entities jointly hold the primary leadership or head position of the same organization, group, or initiative.
- 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_69bd43f9efa081908314cb3e94fa1695 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1dfa3481909d240d50ed0ee38c |
completed | March 20, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69bd6dda5e808190a26ec85e4499d8e4 |
completed | March 20, 2026, 3:55 p.m. |
Created at: March 20, 2026, 1:23 p.m.