Triple
T28007873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tofua |
E707328
|
entity |
| Predicate | formsVolcanicPairWith |
P37537
|
FINISHED |
| Object | Kao |
—
|
NE NERFINISHED |
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: Kao | Statement: [Tofua, formsVolcanicPairWith, Kao]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formsVolcanicPairWith Context triple: [Tofua, formsVolcanicPairWith, Kao]
-
A.
formsVolcanicGroupWith
Indicates that one volcanic feature is associated with another as part of the same volcanic group or complex, typically due to shared origin, structure, or formation history.
-
B.
associatedVolcano
Indicates that there is a specific volcano linked or connected to the referenced entity, such as by location, impact, or relevance.
-
C.
hasTwinVolcano
chosen
Indicates that one volcano is paired with another volcano as its twin, typically implying a close spatial, structural, or formative relationship between them.
-
D.
isVolcanicGroupWith
Indicates that two or more geological features form a related set characterized by volcanic origin or activity.
-
E.
isVolcanic
Indicates that something is characterized by or related to volcanic activity, such as originating from, produced by, or associated with a volcano.
- 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_69ef96ba350c81908230d0b501b974c4 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f6f8565134819096aac0175f924a9f |
completed | May 3, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f6f65fd1d08190b88e5e68ba268500 |
completed | May 3, 2026, 7:16 a.m. |
Created at: April 27, 2026, 8:01 p.m.