Triple
T31704953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type 82 destroyer |
E809152
|
entity |
| Predicate | HMSBristolLaidDown |
P33569
|
FINISHED |
| Object | 1967 |
—
|
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: 1967 | Statement: [Type 82 destroyer, HMSBristolLaidDown, 1967]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HMSBristolLaidDown Context triple: [Type 82 destroyer, HMSBristolLaidDown, 1967]
-
A.
hullConstructedIn
Indicates that the hull of an object (such as a ship or vessel) was built or constructed at a specific location or facility.
-
B.
dateOfKeelLaying
chosen
Indicates the calendar date on which the keel of a vessel was formally laid, marking the official start of its construction.
-
C.
BritishShipRate
Indicates that the subject is classified or rated according to the British naval ship rating system (e.g., first-rate, second-rate, etc.).
-
D.
BritishShipArmamentApproximate
Indicates that a British ship’s armament is specified in approximate rather than exact terms.
-
E.
thirdShipLaunched
Indicates that an entity is the third ship to be launched in a particular sequence or context.
- 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_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:13 p.m.