Triple
T33613729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vulcan to the Sky Trust |
E861057
|
entity |
| Predicate | aircraftTypePreserved |
P1524
|
FINISHED |
| Object | Avro Vulcan B.2 |
—
|
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: Avro Vulcan B.2 | Statement: [Vulcan to the Sky Trust, aircraftTypePreserved, Avro Vulcan B.2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftTypePreserved Context triple: [Vulcan to the Sky Trust, aircraftTypePreserved, Avro Vulcan B.2]
-
A.
aircraftTypeMaintained
Indicates that a maintenance entity performs or is responsible for maintaining a specific type of aircraft.
-
B.
aircraftType
chosen
Indicates the specific model or category of aircraft associated with an entity or event.
-
C.
formerAircraft
Indicates that an entity was previously used or designated as an aircraft but no longer holds that status.
-
D.
aircraftTypesUsedOn
Indicates the types or models of aircraft that are used on or assigned to a particular route, service, operation, or context.
-
E.
poweredAircraftType
Indicates that one entity is a type or category of aircraft that is propelled by an onboard power source (e.g., engines), as opposed to being unpowered.
- 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:41 a.m.