Triple
T9627033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAN VORTAC |
E232494
|
entity |
| Predicate | supportsNavigationSystem |
P35891
|
FINISHED |
| Object | VOR |
—
|
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: VOR | Statement: [SAN VORTAC, supportsNavigationSystem, VOR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNavigationSystem Context triple: [SAN VORTAC, supportsNavigationSystem, VOR]
-
A.
hasNavigationTechnology
chosen
Indicates that an entity is equipped with or utilizes a system or technology for determining or guiding its position, route, or movement.
-
B.
navigationSystemComponent
Indicates that one entity functions as a component or subpart of a navigation system associated with another entity.
-
C.
hasNavigationUse
Indicates that something is used for navigation or serves a navigational function in relation to another entity.
-
D.
hasNavigationCharacteristic
Indicates that an entity possesses a specific property, feature, or quality related to navigation or navigational behavior.
-
E.
navigatesUsing
Indicates that one entity moves or travels through an environment by relying on another entity as its means, tool, or method of navigation.
- 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.