Triple
T2488557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dhuandhar Falls |
E55985
|
entity |
| Predicate | approxHeight |
P38193
|
FINISHED |
| Object | about 10–15 metres |
—
|
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: about 10–15 metres | Statement: [Dhuandhar Falls, approxHeight, about 10–15 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approxHeight Context triple: [Dhuandhar Falls, approxHeight, about 10–15 metres]
-
A.
hasHeight
Indicates that one entity possesses a specific vertical measurement or stature.
-
B.
typicalHeight
Indicates the usual or characteristic height associated with an entity, such as a person, object, or species.
-
C.
heightEstimate
chosen
Indicates an estimated or approximate value for the height of an entity, rather than a precisely measured height.
-
D.
heightReference
Indicates that one entity’s height is being measured, compared, or defined relative to another specified reference point or standard.
-
E.
totalHeight
Indicates the combined vertical measurement resulting from adding the heights of one or more entities.
- 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_69ab49e670a88190b928e08302381710 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd20b6d008190acec0eb172e218c9 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b7cf088190bcff4dac6150044c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.