Triple
T18463366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volcanoes of the World |
E451091
|
entity |
| Predicate | dataStandardization |
P57681
|
FINISHED |
| Object | standardized volcano names |
—
|
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: standardized volcano names | Statement: [Volcanoes of the World, dataStandardization, standardized volcano names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataStandardization Context triple: [Volcanoes of the World, dataStandardization, standardized volcano names]
-
A.
dataStandard
Indicates that there is a defined, agreed-upon specification or convention governing how the related data is structured, formatted, or exchanged.
-
B.
codeStandardization
Indicates that multiple pieces of code are being aligned to a common format, style, or set of conventions to ensure consistency.
-
C.
previouslyStandardizedBy
Indicates that an entity was standardized or formally defined by another entity at some earlier time, but that standardization is no longer current.
-
D.
standardNumberStandardizedBy
Indicates that a standard number has been formally defined, approved, or regulated by a specific standardizing authority or organization.
-
E.
standardizedFeature
chosen
Indicates that a feature has been made consistent and uniform according to a defined standard or specification across relevant entities or contexts.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a8190508190a74b1d3482364905 |
completed | April 19, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:33 a.m.