Triple
T6416283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yuryaku Seamount |
E127836
|
entity |
| Predicate | genesis |
P70536
|
FINISHED |
| Object | shield volcano formed over hotspot |
—
|
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 formed over hotspot | Statement: [Yuryaku Seamount, genesis, shield volcano formed over hotspot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genesis Context triple: [Yuryaku Seamount, genesis, shield volcano formed over hotspot]
-
A.
gens
Indicates a relationship where one entity generates, produces, or gives rise to another entity.
-
B.
generation
Indicates the relationship in which one entity produces, creates, or brings another entity into existence.
-
C.
generationOf
Indicates that one entity is the origin, creator, or producer of another entity.
-
D.
hasCosmogony
Indicates that an entity is associated with, or characterized by, a particular account or doctrine of the origin and development of the universe or cosmos.
-
E.
ethnogenesisOf
Indicates the process or relationship by which a particular group, culture, or people comes into existence or forms its distinct identity.
- 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_69c0083815208190a9b299b8e0640218 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068e89c2c81909eeedc234e8ccde2 |
completed | March 22, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69c060f5d4e481909d1366190607b586 |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623e3cd48190929b0e3cba013909 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:42 p.m.