Triple
T3396879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Owens Lake |
E71549
|
entity |
| Predicate | historicalMaximumDepth |
P4936
|
FINISHED |
| Object | approximately 15 meters |
—
|
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 15 meters | Statement: [Owens Lake, historicalMaximumDepth, approximately 15 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalMaximumDepth Context triple: [Owens Lake, historicalMaximumDepth, approximately 15 meters]
-
A.
maximumDepth
Indicates the greatest extent or deepest level reached by something within a given context or structure.
-
B.
historicalPeak
chosen
Indicates that the related value or state represents the highest level ever reached by something within a historical or recorded time frame.
-
C.
hasMaximumDepth
Indicates that an entity possesses a greatest or limiting depth value beyond which it does not extend.
-
D.
maximumWaterDepth
Indicates the greatest depth of water present or allowed in a given context, such as a location, container, or body of water.
-
E.
maxDepthLocation
Indicates the location at which the maximum depth of something (e.g., an object, structure, or feature) is reached or measured.
- 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_69ad85a9c4a88190a854019341cb3b60 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb8c4099081908a236376b4f86900 |
completed | March 8, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69adadf705608190975423779430cc58 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.