Triple
T6574989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Renmark |
E155537
|
entity |
| Predicate | riverElevation |
P40408
|
FINISHED |
| Object | approximately 31 m above sea level |
—
|
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: approximately 31 m above sea level | Statement: [Renmark, riverElevation, approximately 31 m above sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverElevation Context triple: [Renmark, riverElevation, approximately 31 m above sea level]
-
A.
reservoirElevation
Indicates the height or level of water stored in a reservoir relative to a defined reference point.
-
B.
waterLevelRise
Indicates that the level of water in a given area or container has increased over time.
-
C.
riverMouthElevation
chosen
Indicates the elevation at which a river reaches its mouth or endpoint, typically where it flows into another body of water.
-
D.
elevationAboveWater
Indicates the vertical distance by which one entity is positioned above the surface level of a body of water.
-
E.
floodGauge
Indicates that a device or measurement point is used to monitor and record the level or intensity of flooding at a specific location.
- 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_69c688151254819080387f87deab8fa7 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acf93cb48190b54f5dd6febd34dc |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:53 p.m.