Triple
T10398395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vulcan XH558 |
E245079
|
entity |
| Predicate | returnedToFlight |
P70776
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Vulcan XH558, returnedToFlight, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnedToFlight Context triple: [Vulcan XH558, returnedToFlight, 2007]
-
A.
returnedToFlightStatus
chosen
Indicates that an entity previously grounded, inactive, or suspended has been restored to an approved or operational flight status.
-
B.
returnedToTour
Indicates that an entity resumed or went back to participating in a tour after having left or paused it.
-
C.
returnedVia
Indicates that something was sent back or responded to through a specified medium, channel, or method.
-
D.
associatedWithFlight
Indicates a relationship where an entity is linked or connected to a specific flight, such as by participation, operation, or relevance.
-
E.
performedFlightTo
Indicates that an entity (such as an aircraft or airline) carried out a flight whose destination was a specified location.
- 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_69d381b5116081908d85227bab6d3c0c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9d1f2408190beaa8197641c66b4 |
completed | April 7, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb438c481908dff87c47de2f069 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:07 p.m.