Triple
T24995455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osage Cuestas |
E625555
|
entity |
| Predicate | physiographicSectionOf |
P1962
|
FINISHED |
| Object | Kansas |
—
|
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: Kansas | Statement: [Osage Cuestas, physiographicSectionOf, Kansas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: physiographicSectionOf Context triple: [Osage Cuestas, physiographicSectionOf, Kansas]
-
A.
physiographicDivisionOf
chosen
Indicates that one geographic area is a sub-region or component within the larger physiographic division of another area.
-
B.
physiographicClassificationBy
Indicates a relationship where an entity is assigned a physiographic category or type according to a specified classifier, method, or authority.
-
C.
physiographicSystem
Indicates a relationship where one entity is classified as, or associated with, a particular physiographic system (a distinct large-scale physical landscape or geomorphic region).
-
D.
physicalFeature
Indicates that one entity possesses or exhibits a particular physical characteristic or attribute.
-
E.
topographicalCategory
Indicates the type of landform or surface feature that characterizes the physical terrain 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:04 a.m.