Triple
T9623745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Handley Page Victor |
E232406
|
entity |
| Predicate | retiredFromTankerRole |
P89317
|
FINISHED |
| Object | 1993 |
—
|
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: 1993 | Statement: [Handley Page Victor, retiredFromTankerRole, 1993]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retiredFromTankerRole Context triple: [Handley Page Victor, retiredFromTankerRole, 1993]
-
A.
retiredFrom
Indicates that an entity has permanently stopped working for or being active in a specified organization, role, or activity.
-
B.
retiredFromIcebreakingService
Indicates that an entity has ceased performing icebreaking operations and is no longer in active icebreaking service.
-
C.
retiredFromFrontlineService
Indicates that an entity has ceased active, primary operational duties and is no longer serving in a frontline role.
-
D.
retiredTo
Indicates that an entity has permanently left active service or work and taken up residence or status in a particular place or role as their retirement destination.
-
E.
retiredFromMajorAirlineService
Indicates that an aircraft has been withdrawn from active duty in major commercial airline operations.
- 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_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. |
| PDg | Predicate description generation | batch_69ccd93fc45c8190a823305e461e581d |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:10 p.m.