Triple
T36923940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VEX |
E913283
|
entity |
| Predicate | associatedCallsignOwner |
P89103
|
FINISHED |
| Object | Virgin Express |
E265982
|
NE 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: Virgin Express | Statement: [VEX, associatedCallsignOwner, Virgin Express]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCallsignOwner Context triple: [VEX, associatedCallsignOwner, Virgin Express]
-
A.
relatedCallsignUsage
Indicates that one callsign is used in connection with, or as a variant of, another callsign in operational or identification contexts.
-
B.
hasCallSignOwner
chosen
Indicates that a particular call sign is owned or assigned to a specific entity.
-
C.
callsignOfOperator
Indicates that one entity is the radio or communication callsign assigned to or used by another entity acting as an operator.
-
D.
inspiredCallsignOf
Indicates that one entity’s callsign was created based on, influenced by, or derived from another entity.
-
E.
callsign
Indicates that an entity is assigned or uses a specific radio or identification callsign as its designated identifier in communication contexts.
- F. None of above.
Provenance (4 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_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e2c2c1890819097dd8a82b2428fca |
completed | June 26, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.