Triple
T979547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Handley Page O/400 |
E21134
|
entity |
| Predicate | retiredFromService |
P2089
|
FINISHED |
| Object | early 1920s |
—
|
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: early 1920s | Statement: [Handley Page O/400, retiredFromService, early 1920s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retiredFromService Context triple: [Handley Page O/400, retiredFromService, early 1920s]
-
A.
retiredFrom
Indicates that an entity has permanently stopped working for or being active in a specified organization, role, or activity.
-
B.
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.
-
C.
retired
chosen
Indicates that an entity has permanently stopped working in their former occupation or role, typically after reaching a certain age or service duration.
-
D.
returnedFromRetirement
Indicates that an entity has resumed an activity, role, or position after having previously retired from it.
-
E.
forcedToRetire
Indicates that an entity was compelled, rather than choosing voluntarily, to end their professional role or career.
- 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_69a493c2b62c8190b616351789ec47f8 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b479e8f081908183448c36244e1f |
completed | March 1, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a8a3b08190b4538e119b13f7f5 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:40 p.m.