Triple
T34983033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torre Central |
E1008865
|
entity |
| Predicate | erosionShapedBy |
P103214
|
FINISHED |
| Object | glacial processes |
—
|
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: glacial processes | Statement: [Torre Central, erosionShapedBy, glacial processes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: erosionShapedBy Context triple: [Torre Central, erosionShapedBy, glacial processes]
-
A.
erosionAgent
chosen
Indicates the natural force or process responsible for wearing away, transporting, or reshaping material from a surface.
-
B.
erosionRate
Indicates the rate at which material is worn away or removed from a surface over time due to erosive processes.
-
C.
hasErosionEffect
Indicates that one entity causes or exhibits an erosive impact or degradation effect on another entity or surface.
-
D.
hasErosionRole
Indicates that an entity participates in or contributes to an erosion process in a specified role or capacity.
-
E.
hasErosionFeature
Indicates that one entity exhibits or contains a specific erosion-related feature or form resulting from erosional processes.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.