Triple
T32202406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Humphreys |
E822577
|
entity |
| Predicate | onBoundary |
P67212
|
FINISHED |
| Object | Inyo County, California |
—
|
NE NERFINISHED |
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: Inyo County, California | Statement: [Mount Humphreys, onBoundary, Inyo County, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onBoundary Context triple: [Mount Humphreys, onBoundary, Inyo County, California]
-
A.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
B.
onBorderBetween
Indicates that an entity is located along or directly adjacent to the dividing line shared by two distinct regions or areas.
-
C.
liesOnBorderOf
chosen
Indicates that one entity is located along or directly adjacent to the boundary line separating it from another entity.
-
D.
hasBoundaryCriterion
Indicates that something is associated with a specific rule or condition used to define or limit its boundary.
-
E.
hasNearbyBoundary
Indicates that one entity’s boundary lies close to, but does not necessarily touch or coincide with, the boundary of another entity.
- 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bb3c8d7081909b960e469e4d8504 |
completed | May 3, 2026, 3:04 a.m. |
| PD | Predicate disambiguation | batch_69f6b3aa892481908d29283a074e6722 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:36 a.m.