Triple
T2859583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivanpah Dry Lake |
E63285
|
entity |
| Predicate | proximityToBorder |
P31353
|
FINISHED |
| Object | near Nevada–California border |
—
|
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: near Nevada–California border | Statement: [Ivanpah Dry Lake, proximityToBorder, near Nevada–California border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proximityToBorder Context triple: [Ivanpah Dry Lake, proximityToBorder, near Nevada–California border]
-
A.
distanceToBorder
chosen
Indicates the measured or estimated spatial separation between a given entity or location and the nearest relevant border or boundary.
-
B.
borderStateNearby
Indicates that one state is geographically close to, but does not necessarily directly touch, the border of another state.
-
C.
closerTo
Indicates that one entity is at a smaller distance to a reference entity than another entity is.
-
D.
operatesOnBorderWith
Indicates that one entity conducts activities or exerts influence along or across the shared border it has with another entity.
-
E.
countryBorderProximity
Indicates that one country is geographically close to or directly bordering another country.
- 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_69ab4c41e8c08190a9e8f5249cc12610 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf8aec3c8190a4168d8c916b5268 |
completed | March 7, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69abdd10aef88190b750aae07e7df4dc |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.