Triple
T15473108
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shira volcanic cone |
E376712
|
entity |
| Predicate | hasProcessHistory |
P25192
|
FINISHED |
| Object | extensive 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: extensive erosion | Statement: [Shira volcanic cone, hasProcessHistory, extensive erosion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProcessHistory Context triple: [Shira volcanic cone, hasProcessHistory, extensive erosion]
-
A.
hasHistoricalProcess
chosen
Indicates that an entity is associated with, or characterized by, a historical process or sequence of events that unfolded over time.
-
B.
hasHistoryIn
Indicates that an entity has a past involvement, presence, or record of activity within a particular domain, context, or location.
-
C.
hasHistoryPeriod
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
-
D.
hasHistorySince
Indicates that an entity has maintained a particular state, condition, or relationship continuously starting from a specified point in time.
-
E.
hasResourceHistory
Indicates that an entity is associated with a record or sequence of past states, usages, or changes of a particular resource over time.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f6c57308190b4cfe661c26addd4 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:33 a.m.