Triple
T25136525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanaga Volcano |
E629672
|
entity |
| Predicate | hasVolcanoNumberingSystem |
P5213
|
FINISHED |
| Object | USGS volcano catalog |
—
|
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: USGS volcano catalog | Statement: [Tanaga Volcano, hasVolcanoNumberingSystem, USGS volcano catalog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVolcanoNumberingSystem Context triple: [Tanaga Volcano, hasVolcanoNumberingSystem, USGS volcano catalog]
-
A.
hasNumberSystem
chosen
Indicates that an entity possesses or uses a particular system for representing and organizing numbers.
-
B.
hasVolcano
Indicates that one entity possesses, contains, or is the location of a volcano.
-
C.
volcanoNumber
Indicates that an entity is assigned a specific identifying number within a system or catalog of volcanoes.
-
D.
laterNumberingSystem
Indicates that one numbering system was adopted or used after another, reflecting a subsequent or more recent scheme of numbering.
-
E.
followsCountingSystemOf
Indicates that one entity uses or adheres to the same counting or numeral system as another entity.
- 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_69e2ff338250819096ff6c8892804389 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 6:29 a.m.