Triple
T9108114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tajo Basin |
E218526
|
entity |
| Predicate | surfaceProcesses |
P70119
|
FINISHED |
| Object | fluvial 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: fluvial erosion | Statement: [Tajo Basin, surfaceProcesses, fluvial erosion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceProcesses Context triple: [Tajo Basin, surfaceProcesses, fluvial erosion]
-
A.
surfaceManagement
Indicates the management or control exercised over the surface of an area, object, or environment, such as its use, maintenance, or treatment.
-
B.
surfaceAccess
Indicates that one entity provides a means for another entity to reach, enter, or interact with a surface or outer layer.
-
C.
surfaceOperation
chosen
Indicates an operation or activity that is performed on or at the surface of an object, material, or environment.
-
D.
surfaceState
Indicates the physical condition or status of a surface, such as its texture, cleanliness, damage, or treatment at a given time.
-
E.
surfaceBehavior
Indicates how an entity behaves or interacts specifically at or on its surface.
- 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_69ca83db7448819090d0a5de842ef2ac |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca57543448190829853c31e05dd8c |
completed | April 1, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69cc65fe5be081909d4470d6317b14a6 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:16 p.m.