Triple
T9627045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAN VORTAC |
E232494
|
entity |
| Predicate | supportsProcedureType |
P24486
|
FINISHED |
| Object | instrument approach procedures |
—
|
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: instrument approach procedures | Statement: [SAN VORTAC, supportsProcedureType, instrument approach procedures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsProcedureType Context triple: [SAN VORTAC, supportsProcedureType, instrument approach procedures]
-
A.
supportsType
chosen
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
B.
supportsProgramType
Indicates that one entity is capable of handling, offering, or being compatible with a specified type of program.
-
C.
supportsTargetType
Indicates that one entity is capable of operating with, handling, or being compatible with a specified target type.
-
D.
supportsDriverType
Indicates that one entity is compatible with, or able to operate using, a specified type of driver.
-
E.
supportsPluginType
Indicates that one entity is capable of working with, handling, or being compatible with a specified type of plugin.
- 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_69ca848793ec8190a93a12383a754dc0 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9afc9144819084b208c3d04174ba |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:10 p.m.