Triple
T29453614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICAO volcanic ash advisory format |
E747041
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | standardized reporting format |
C24797
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: standardized reporting format Context triple: [ICAO volcanic ash advisory format, instanceOf, standardized reporting format]
-
A.
standardized form
chosen
A standardized form is a pre-designed, uniform document or template used to consistently collect, organize, and process specific types of information across multiple instances or users.
-
B.
standardized healthcare document
A standardized healthcare document is a formally structured record that captures patient, clinical, or administrative health information in a consistent, interoperable format for use across providers, systems, and settings.
-
C.
regulatory reporting platform
A regulatory reporting platform is a system that collects, validates, and transforms organizational data into compliant reports for submission to regulators according to applicable rules and deadlines.
-
D.
standardization scheme
A standardization scheme is a structured framework of rules, formats, and procedures designed to ensure consistency, compatibility, and interoperability across systems, processes, or data.
-
E.
standardized code
A standardized code is a formally defined, widely accepted set of symbols or rules used to represent information consistently across systems, organizations, or contexts.
- F. None of above.
Provenance (1 batch)
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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 3:34 p.m.