Triple
T26352795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fish River Canyon |
E662945
|
entity |
| Predicate | formedByProcesses |
P972
|
FINISHED |
| Object | river erosion |
—
|
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: river erosion | Statement: [Fish River Canyon, formedByProcesses, river erosion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedByProcesses Context triple: [Fish River Canyon, formedByProcesses, river erosion]
-
A.
formedBy
chosen
Indicates that something comes into existence or is created as a result of a specific agent, process, or combination of components.
-
B.
formedByParty
Indicates that something (such as an organization, group, or entity) has been created, established, or constituted by a specific party.
-
C.
formedByConvergenceOf
Indicates that something comes into existence or is created as a result of multiple elements, paths, or processes coming together and uniting.
-
D.
basedOnProcess
Indicates that something is derived from, determined by, or dependent on a particular process or sequence of actions.
-
E.
modifiedByProcess
Indicates that an entity has been changed or altered as a result of a specific process.
- 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 26, 2026, 10:46 p.m.