Triple
T31670924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dambusters |
E808265
|
entity |
| Predicate | laterAircraftUsed |
P199875
|
FINISHED |
| Object | Avro Vulcan |
—
|
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 | Statement: [Dambusters, laterAircraftUsed, Avro Vulcan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterAircraftUsed Context triple: [Dambusters, laterAircraftUsed, Avro Vulcan]
-
A.
previousAircraftUsed
Indicates that one aircraft was used immediately before another in a sequence of aircraft usage.
-
B.
formerAircraft
Indicates that an entity was previously used or designated as an aircraft but no longer holds that status.
-
C.
aircraftTypesUsedOn
Indicates the types or models of aircraft that are used on or assigned to a particular route, service, operation, or context.
-
D.
referredAircraftUsedIn
Indicates that an aircraft being referred to is the one that was actually used in a particular event, operation, or context.
-
E.
referredAircraftUsedFor
Indicates that the referenced aircraft is utilized for a particular purpose, role, or operation in relation to another entity or context.
- 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ff6074bcd4819090b72cd6209ff206 |
completed | May 9, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69ff600aba888190812a6e7eca0283b8 |
completed | May 9, 2026, 4:25 p.m. |
| PDg | Predicate description generation | batch_69ff607407a881909d9e6e1c98559a6e |
completed | May 9, 2026, 4:27 p.m. |
Created at: April 30, 2026, 11:01 p.m.