Triple
T14211139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawkesbury Sandstone |
E352233
|
entity |
| Predicate | erosionResistance |
P113228
|
FINISHED |
| Object | high |
—
|
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: high | Statement: [Hawkesbury Sandstone, erosionResistance, high]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: erosionResistance Context triple: [Hawkesbury Sandstone, erosionResistance, high]
-
A.
hasErosionFeature
Indicates that one entity exhibits or contains a specific erosion-related feature or form resulting from erosional processes.
-
B.
erosionAgent
Indicates the natural force or process responsible for wearing away, transporting, or reshaping material from a surface.
-
C.
isCorrosionResistantInAir
Indicates that an entity maintains its integrity and does not significantly corrode when exposed to air under specified conditions.
-
D.
dustResistanceRating
Indicates the level or degree to which something is protected against or unaffected by dust.
-
E.
designedToWithstand
Indicates that something has been intentionally created or engineered to resist, endure, or remain functional under specified conditions, forces, or stresses.
- F. None of above. chosen
Provenance (4 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_69d8278a06e481908b5d6af0a8afe737 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de620dba0c8190bb77a1df10e1d3a7 |
completed | April 14, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69de05bcd7d48190a4848d9320404aa6 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 1:05 a.m.