Triple
T1115809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angel Falls |
E11096
|
entity |
| Predicate | erosionType |
P18790
|
FINISHED |
| Object | fluvial erosion of sandstone |
—
|
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: fluvial erosion of sandstone | Statement: [Angel Falls, erosionType, fluvial erosion of sandstone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: erosionType Context triple: [Angel Falls, erosionType, fluvial erosion of sandstone]
-
A.
geomorphologicalProcess
chosen
Indicates a relationship where one entity undergoes or is shaped by natural earth-surface processes that modify landforms and terrain structure.
-
B.
typeOfSedimentation
Indicates the specific kind or process of sediment deposition or settling that characterizes how sediment accumulates in a given context.
-
C.
typeOfDam
Indicates the specific kind or classification of a dam associated with an entity.
-
D.
elevationType
Indicates the kind or classification of elevation associated with an entity, such as how its height or altitude is characterized.
-
E.
excavationType
Indicates the specific method or category of excavation associated with an entity or activity.
- 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bbd92a8c8190a16e55f3f739010f |
completed | March 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69a4bb42990c819080db96478fd4977e |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:43 p.m.