Triple
T28160631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Logan County, Arkansas |
E714881
|
entity |
| Predicate | mountMagazineElevation_ft |
P45909
|
FINISHED |
| Object | 2753 |
—
|
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: 2753 | Statement: [Logan County, Arkansas, mountMagazineElevation_ft, 2753]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountMagazineElevation_ft Context triple: [Logan County, Arkansas, mountMagazineElevation_ft, 2753]
-
A.
damCrestElevation
Indicates the height of the top (crest) of a dam above a specified reference level, typically sea level.
-
B.
upperStationElevation
Indicates the elevation or height above a reference level (e.g., sea level) of the upper station in a system or structure.
-
C.
elevationApproxMeters
chosen
Indicates the approximate elevation of an entity above sea level, measured in meters.
-
D.
elevationBy
Indicates a relationship where one entity raises, increases, or enhances the level, status, or intensity of another entity.
-
E.
hasElevationFeature
Indicates that one entity possesses or is characterized by a particular elevation-related feature or attribute, such as height, altitude, or vertical relief.
- 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_69efd6b156448190bfa15958208395c3 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 10:06 p.m.