Triple
T385567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inyo County, California |
E8772
|
entity |
| Predicate | hasExtreme |
P8205
|
FINISHED |
| Object | contains highest point in contiguous United States |
—
|
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: contains highest point in contiguous United States | Statement: [Inyo County, California, hasExtreme, contains highest point in contiguous United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasExtreme Context triple: [Inyo County, California, hasExtreme, contains highest point in contiguous United States]
-
A.
hasPar
Indicates a relationship where one entity has another entity as its parent.
-
B.
hasExclave
Indicates that a territory or administrative unit possesses an exclave—part of its area that is geographically separated from its main portion and surrounded by foreign territory.
-
C.
hasPeak
chosen
Indicates that something possesses or contains a highest point, summit, or maximum value.
-
D.
hadFort
Indicates that an entity possessed, controlled, or contained a fort at some time.
-
E.
hasDam
Indicates that a watercourse, reservoir, or similar feature is impounded or controlled by a specific dam.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec4345a48190a413261cba4eafd7 |
completed | Feb. 28, 2026, 1:23 p.m. |
| PD | Predicate disambiguation | batch_69a2e967d84c8190a6b647f78d95d4e4 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.