Triple
T17684154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B53 nuclear bomb |
E440845
|
entity |
| Predicate | removedFromActiveService |
P128566
|
FINISHED |
| Object | early 1980s |
—
|
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 1980s | Statement: [B53 nuclear bomb, removedFromActiveService, early 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: removedFromActiveService Context triple: [B53 nuclear bomb, removedFromActiveService, early 1980s]
-
A.
removedFrom
Indicates that one entity has been taken away, extracted, or detached from another entity or context.
-
B.
removedFromSuccession
Indicates that an entity has been formally excluded from a previously held position in a line of succession.
-
C.
retiredFromBRService
Indicates that an entity has ceased active service or operation within the British Rail (BR) system.
-
D.
removedOn
Indicates that an entity was taken away, deleted, or detached at a specific point in time.
-
E.
removedFromPublicDuties
Indicates that an entity has been taken out of roles or responsibilities that involve serving or representing the public.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4704710488190826aaf0bdd4b2088 |
completed | April 19, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 10:02 a.m.