Triple
T29145504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VAAC Anchorage |
E738760
|
entity |
| Predicate | advisoryFormat |
P130
|
FINISHED |
| Object | standard ICAO volcanic ash advisory format |
—
|
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: standard ICAO volcanic ash advisory format | Statement: [VAAC Anchorage, advisoryFormat, standard ICAO volcanic ash advisory format]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: advisoryFormat Context triple: [VAAC Anchorage, advisoryFormat, standard ICAO volcanic ash advisory format]
-
A.
format
chosen
Indicates the specific arrangement, structure, or presentation style in which something is organized or expressed.
-
B.
safetyFormat
Indicates that one entity specifies or conforms to a particular format, standard, or structure related to safety.
-
C.
usedFormat
Indicates that one entity employs or applies a particular format or representation in relation to another entity.
-
D.
editorialFormat
Indicates the specific editorial style, layout, or presentation format in which content is produced or published.
-
E.
deciderFormat
Indicates the format or representation in which a decision or choice is expressed or encoded.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f66271fc4c81908824de34290609d6 |
completed | May 2, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f65c2376a08190be5215171e908e69 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:39 a.m.