Triple
T35661196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villamayor sandstone |
E1030437
|
entity |
| Predicate | weatheringIssues |
P56098
|
FINISHED |
| Object | surface 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: surface erosion | Statement: [Villamayor sandstone, weatheringIssues, surface erosion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weatheringIssues Context triple: [Villamayor sandstone, weatheringIssues, surface erosion]
-
A.
weatheringProduct
Indicates the substance that results from the weathering or breakdown of another material.
-
B.
weatheringStyle
chosen
Indicates the characteristic manner or pattern in which something undergoes weathering or surface degradation over time.
-
C.
hasWeathering
Indicates that one entity undergoes or exhibits the process of weathering caused by another entity or environmental factors.
-
D.
erosionConcern
Indicates concern that a location, structure, or resource is being or may be negatively affected by erosion.
-
E.
conditionIssues
Indicates that one entity has problems, defects, or concerns related to the state or condition of another entity.
- 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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79fa7d1708190bb5defe2ea54dc75 |
completed | May 3, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.