Triple
T12708660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Covehithe |
E303654
|
entity |
| Predicate | erosionStatus |
P84293
|
FINISHED |
| Object | rapidly eroding |
—
|
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: rapidly eroding | Statement: [Covehithe, erosionStatus, rapidly eroding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: erosionStatus Context triple: [Covehithe, erosionStatus, rapidly eroding]
-
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.
eroded
Indicates that a force or process has gradually worn away, diminished, or degraded something over time.
-
D.
geologicalStatus
Indicates the current geological condition or classification of an entity, such as its formation state, activity level, or structural status within the Earth’s crust.
-
E.
destructionStatus
chosen
Indicates the condition or extent to which something has been damaged, ruined, or rendered unusable.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96207b2d881908314efc3e350aa78 |
completed | April 10, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69d960c088dc8190b0e63312c54e4c6c |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:23 p.m.