Triple
T23347384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Mesa Summit Trail |
E591903
|
entity |
| Predicate | summitMarkerInscription |
P48886
|
FINISHED |
| Object | indicates highest point in Oklahoma |
—
|
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: indicates highest point in Oklahoma | Statement: [Black Mesa Summit Trail, summitMarkerInscription, indicates highest point in Oklahoma]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitMarkerInscription Context triple: [Black Mesa Summit Trail, summitMarkerInscription, indicates highest point in Oklahoma]
-
A.
hasSummitMarker
chosen
Indicates that a location or peak is marked by an official summit marker or sign denoting its highest point.
-
B.
summitRepresents
Indicates that a summit serves as a formal venue or occasion in which certain positions, interests, or entities are presented, symbolized, or spoken for.
-
C.
summitShape
Indicates the geometric form or contour that characterizes the topmost point or summit of an object or landform.
-
D.
summitResembles
Indicates that one summit is similar in appearance or characteristics to another summit.
-
E.
summitCount
Indicates the number of summits or peak ascents associated with an 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1983840a481908c503e47ef2158e3 |
completed | April 29, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:19 p.m.