Triple
T31704955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type 82 destroyer |
E809152
|
entity |
| Predicate | HMSBristolCommissioned |
P150871
|
FINISHED |
| Object | 1973 |
—
|
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: 1973 | Statement: [Type 82 destroyer, HMSBristolCommissioned, 1973]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HMSBristolCommissioned Context triple: [Type 82 destroyer, HMSBristolCommissioned, 1973]
-
A.
capturedAndCommissioned
Indicates that one entity has taken control of another (often by force) and then formally put it into service or use under its authority.
-
B.
shipCommissionedAs
Indicates that a ship entered active service under a specific name or designation at the time of its commissioning.
-
C.
hullConstructedIn
Indicates that the hull of an object (such as a ship or vessel) was built or constructed at a specific location or facility.
-
D.
commissionedShip
Indicates that a ship has been formally placed into active service, typically following its construction or acquisition.
-
E.
shipCommissionedDate
chosen
Indicates the date on which a ship was officially commissioned into service.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b49436b0819094e21603054d05d4 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: April 30, 2026, 11:13 p.m.