Triple
T25624673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massif Central foothills |
E642394
|
entity |
| Predicate | processShapedBy |
P137014
|
FINISHED |
| Object | fluvial incision |
—
|
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 incision | Statement: [Massif Central foothills, processShapedBy, fluvial incision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: processShapedBy Context triple: [Massif Central foothills, processShapedBy, fluvial incision]
-
A.
shapedByEvent
Indicates that something’s form, state, or characteristics are influenced or determined by a particular event.
-
B.
shaped
Indicates that one entity has given form, contour, or structure to another entity or outcome.
-
C.
handleShape
Indicates that an entity is responsible for processing, managing, or otherwise dealing with a particular shape.
-
D.
shapeInfluencedBy
chosen
Indicates that the form or outline of one entity is affected, determined, or modified by another entity or factor.
-
E.
seeksToShape
Indicates an entity’s intention or effort to influence, mold, or determine the form, direction, or outcome of another entity or situation.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 5:07 p.m.