Triple
T5854114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meiji Seamount |
E130107
|
entity |
| Predicate | hotspotTrackRole |
P45408
|
FINISHED |
| Object | records early part of Hawaiian hotspot track |
—
|
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: records early part of Hawaiian hotspot track | Statement: [Meiji Seamount, hotspotTrackRole, records early part of Hawaiian hotspot track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hotspotTrackRole Context triple: [Meiji Seamount, hotspotTrackRole, records early part of Hawaiian hotspot track]
-
A.
isHotspotTrackOf
Indicates that one entity is a hotspot track that corresponds to, or is derived from, another entity.
-
B.
hotspot
Indicates that a location or entity is a focal point of intense activity, interest, or occurrence relative to others.
-
C.
trackRole
chosen
Indicates that an entity holds or performs a specific role within the context of a particular track or sequence of activities.
-
D.
hotspotType
Indicates the specific category or kind of hotspot associated with an entity or location.
-
E.
trackOn
Indicates that one entity is physically positioned or moving along the surface or path of another, like a vehicle on a track or rails.
- 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_69c0084de39081909eb34e6bed74215a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03345ca0c819081c81148d054fed2 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:55 p.m.