Triple
T1007992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hawaiian–Emperor seamount chain |
E21756
|
entity |
| Predicate | hotspotType |
P23547
|
FINISHED |
| Object | intraplate 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: intraplate hotspot | Statement: [Hawaiian–Emperor seamount chain, hotspotType, intraplate hotspot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hotspotType Context triple: [Hawaiian–Emperor seamount chain, hotspotType, intraplate hotspot]
-
A.
networkType
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
-
B.
spurType
Indicates the specific kind or category of spur associated with or used by an entity.
-
C.
featureType
Indicates the specific kind or category of feature that characterizes or distinguishes an entity.
-
D.
hostsUnitType
Indicates that one entity serves as a location or platform that accommodates or contains a specified type of unit.
-
E.
homeKitType
Indicates the specific HomeKit category or type assigned to a device or accessory within the HomeKit ecosystem.
- 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_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. |
| PDg | Predicate description generation | batch_69a4b7f2d1b081908eb2df54e91c8c1d |
completed | March 1, 2026, 10:04 p.m. |
Created at: March 1, 2026, 7:41 p.m.