Triple
T24174691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenton, Oklahoma |
E599245
|
entity |
| Predicate | hasHighestPointOfStateNearby |
P50804
|
FINISHED |
| Object | Black Mesa summit |
—
|
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: Black Mesa summit | Statement: [Kenton, Oklahoma, hasHighestPointOfStateNearby, Black Mesa summit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighestPointOfStateNearby Context triple: [Kenton, Oklahoma, hasHighestPointOfStateNearby, Black Mesa summit]
-
A.
hasHighestPointNear
chosen
Indicates that one entity’s highest point is located close to another specified entity or location.
-
B.
hasMountainPassNearby
Indicates that a mountain pass is located in close proximity to the referenced place or feature.
-
C.
hasNearestMountain
Indicates that one entity is the closest mountain geographically relative to another entity.
-
D.
isClosestStateHighPointTo
Indicates that one state high point is geographically nearer to a given reference location or feature than any other state high point.
-
E.
containsHighestPointOf
Indicates that one entity includes within its boundaries the location of the highest point 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:33 p.m.