Triple
T1008008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawaiian–Emperor seamount chain |
E21756
|
entity |
| Predicate | formedByProcess |
P972
|
FINISHED |
| Object | shield volcano construction |
—
|
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: shield volcano construction | Statement: [Hawaiian–Emperor seamount chain, formedByProcess, shield volcano construction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedByProcess Context triple: [Hawaiian–Emperor seamount chain, formedByProcess, shield volcano construction]
-
A.
formedBy
chosen
Indicates that something comes into existence or is created as a result of a specific agent, process, or combination of components.
-
B.
basedOnProcess
Indicates that something is derived from, determined by, or dependent on a particular process or sequence of actions.
-
C.
partOfProcess
Indicates that one event, step, or action occurs as a component or stage within a larger overall process.
-
D.
formedByInstrument
Indicates that something is created, produced, or brought into existence through the use or action of a specific instrument or tool.
-
E.
initiatedBy
Indicates that an action, event, or process was started or set in motion by a particular 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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b7f4c66c8190b6098fb72c1465a3 |
completed | March 1, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69a4b7203124819091de68cba5f731c1 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:41 p.m.