Triple
T9623744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Handley Page Victor |
E232406
|
entity |
| Predicate | retiredFromBomberRole |
P35163
|
FINISHED |
| Object | late 1960s |
—
|
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: late 1960s | Statement: [Handley Page Victor, retiredFromBomberRole, late 1960s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retiredFromBomberRole Context triple: [Handley Page Victor, retiredFromBomberRole, late 1960s]
-
A.
retiredFromRAAFService
Indicates that an individual has ended or concluded their period of service in the Royal Australian Air Force.
-
B.
retiredFromMajorAirlineService
Indicates that an aircraft has been withdrawn from active duty in major commercial airline operations.
-
C.
retiredFromFrontlineService
chosen
Indicates that an entity has ceased active, primary operational duties and is no longer serving in a frontline role.
-
D.
retiredFrom
Indicates that an entity has permanently stopped working for or being active in a specified organization, role, or activity.
-
E.
retiredFromMajorAirlines
Indicates that a person has ended their professional employment or active service with a major commercial airline company.
- 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_69ca848793ec8190a93a12383a754dc0 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9ad650a4819096258665bc3f410b |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5aa1d2c8190a287bf1cf4a3037e |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:10 p.m.