Triple
T10078488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rio Chama |
E213834
|
entity |
| Predicate | hasGeologicalFeatureAlong |
P940
|
FINISHED |
| Object | canyon |
—
|
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: canyon | Statement: [Rio Chama, hasGeologicalFeatureAlong, canyon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeologicalFeatureAlong Context triple: [Rio Chama, hasGeologicalFeatureAlong, canyon]
-
A.
hasNaturalFeature
Indicates that one entity possesses, contains, or is characterized by a particular natural feature (such as a mountain, river, forest, or coastline).
-
B.
hasLandform
chosen
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
C.
isPartOfTectonicFeature
Indicates that one geological entity is a component or subdivision of a larger tectonic feature or structure.
-
D.
tectonicFeaturesPresence
Indicates the existence or occurrence of tectonic features (such as faults, folds, or plate boundaries) in a specified area or context.
-
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_69ca839bf730819086900c323c9b8c95 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd030a0fc819084b523e8e63636fa |
completed | April 2, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69cd4b97870481908f7a89df10d58a9e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9 p.m.