Triple
T29526289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G-VWOW |
E749076
|
entity |
| Predicate | tailNumberUsage |
P166997
|
FINISHED |
| Object | used by Virgin Atlantic |
—
|
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: used by Virgin Atlantic | Statement: [G-VWOW, tailNumberUsage, used by Virgin Atlantic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tailNumberUsage Context triple: [G-VWOW, tailNumberUsage, used by Virgin Atlantic]
-
A.
tailNumberFormat
Indicates the standardized pattern or structure used to represent an aircraft’s tail number identifier.
-
B.
tailNumberPrefix
Indicates that one entity’s tail number begins with the specified prefix represented by the other entity.
-
C.
aircraftRegistration
Indicates that an aircraft is assigned a specific official registration identifier or code.
-
D.
fleetNumbers
Indicates that there is an association between an entity and one or more identifying numbers assigned to it as part of a fleet.
-
E.
usedByAircraftRegisteredIn
Indicates that something (such as equipment, a system, or a facility) is utilized by aircraft that are registered in a specified jurisdiction or registry.
- F. None of above. chosen
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_69f0bd46d99c81908ba9d01cc1dbef7d |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c9d5df48190ad10afb467a9c7a6 |
completed | May 2, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6642e676c8190af0e6b1416eed6d2 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 28, 2026, 4:46 p.m.