Triple
T36923929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virgin Express |
E913283
|
entity |
| Predicate | usedICAODesignator |
P175188
|
FINISHED |
| Object | VEX |
—
|
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: VEX | Statement: [Virgin Express, usedICAODesignator, VEX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedICAODesignator Context triple: [Virgin Express, usedICAODesignator, VEX]
-
A.
operatesUnderICAODesignator
chosen
Indicates that an airline or aviation operator conducts its operations using a specific ICAO-assigned designator code.
-
B.
usesDesignator
Indicates that one entity employs or references a specific designator (such as a name, code, or identifier) to denote or refer to another entity.
-
C.
AVADesignation
Indicates that an entity has been assigned a specific AVA (American Viticultural Area) designation, linking it to a formally recognized wine-growing region.
-
D.
usesServiceDesignation
Indicates that one entity adopts or applies a particular service designation associated with another entity or offering.
-
E.
hasICAOLocationIndicator
Indicates that an entity is associated with a specific ICAO location indicator code, typically identifying an airport or aerodrome in the ICAO system.
- 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_69f76e885b848190bad82c87e9525486 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ff1f3f94fc819095955299f50ab4ce |
completed | May 9, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69ff1ea47748819082f63d9b9d9c3e65 |
completed | May 9, 2026, 11:46 a.m. |
Created at: May 3, 2026, 4:13 p.m.