Triple
T29249328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toussidé crater |
E741517
|
entity |
| Predicate | associatedVolcanicMassif |
P47953
|
FINISHED |
| Object | Tarso Toussidé |
E202495
|
NE 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: Tarso Toussidé | Statement: [Toussidé crater, associatedVolcanicMassif, Tarso Toussidé]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedVolcanicMassif Context triple: [Toussidé crater, associatedVolcanicMassif, Tarso Toussidé]
-
A.
associatedVolcano
Indicates that there is a specific volcano linked or connected to the referenced entity, such as by location, impact, or relevance.
-
B.
isStratovolcanoOf
Indicates that a volcano is a stratovolcano specifically associated with, or located on, a particular geographic or administrative entity.
-
C.
isVolcanicEdificeOn
Indicates that a volcanic edifice is physically located on or built upon a specified surface or geological feature.
-
D.
isPartOfVolcanicSystem
chosen
Indicates that one entity belongs to, or is a component within, a larger volcanic system or complex.
-
E.
isVolcanicGroupWith
Indicates that two or more geological features form a related set characterized by volcanic origin or activity.
- F. None of above.
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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_6a033d975d788190aafc4be10d6c5c1c |
completed | May 12, 2026, 2:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a258925827c819094b5cb59e98790b4 |
completed | June 7, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_6a033cc2668481908cb696e57632a68f |
completed | May 12, 2026, 2:44 p.m. |
Created at: April 28, 2026, 12:33 p.m.