Triple
T27033325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goosenecks State Park |
E680982
|
entity |
| Predicate | landformTypeObserved |
P940
|
FINISHED |
| Object | incised meanders |
—
|
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: incised meanders | Statement: [Goosenecks State Park, landformTypeObserved, incised meanders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landformTypeObserved Context triple: [Goosenecks State Park, landformTypeObserved, incised meanders]
-
A.
hasLandform
chosen
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
B.
landerType
Indicates the specific kind or category of lander involved in the relationship or action.
-
C.
topographicalCategory
Indicates the type of landform or surface feature that characterizes the physical terrain associated with an entity.
-
D.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
-
E.
geologicalFormation
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6223870308190a016b76902bcf6d4 |
completed | May 2, 2026, 4:11 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 7:15 a.m.