Triple
T13326292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upholder-class submarine |
E317449
|
entity |
| Predicate | serviceRetirementFromRoyalNavy |
P35163
|
FINISHED |
| Object | 1994 |
—
|
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: 1994 | Statement: [Upholder-class submarine, serviceRetirementFromRoyalNavy, 1994]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceRetirementFromRoyalNavy Context triple: [Upholder-class submarine, serviceRetirementFromRoyalNavy, 1994]
-
A.
intendedToReplaceInRoyalNavy
Indicates that one entity was planned or designated to take over the role, duties, or position of another entity within the Royal Navy.
-
B.
retiredFromFrontlineService
chosen
Indicates that an entity has ceased active, primary operational duties and is no longer serving in a frontline role.
-
C.
enteredRoyalNavyFrontlineService
Indicates that an entity began active duty or operational deployment in the frontline forces of the Royal Navy.
-
D.
joinedRoyalNavy
Indicates that an individual entered into service as a member of the Royal Navy.
-
E.
retiredFromRAAFService
Indicates that an individual has ended or concluded their period of service in the Royal Australian Air Force.
- 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_69d806b4d62c81908d4ced1665414be5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6babd88190a5d529df9584b9a4 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:30 p.m.