Triple
T31704927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type 82 destroyer |
E809152
|
entity |
| Predicate | onlyCompletedShip |
P172449
|
FINISHED |
| Object | HMS Bristol |
—
|
NE NERFINISHED |
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: HMS Bristol | Statement: [Type 82 destroyer, onlyCompletedShip, HMS Bristol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onlyCompletedShip Context triple: [Type 82 destroyer, onlyCompletedShip, HMS Bristol]
-
A.
shipCompleted
Indicates that a shipping process or delivery has been fully completed for the associated item or order.
-
B.
shipsWith
Indicates that one entity is delivered, packaged, or provided together with another entity as part of the same shipment or bundle.
-
C.
commissionedShip
Indicates that a ship has been formally placed into active service, typically following its construction or acquisition.
-
D.
servedShip
Indicates that one entity performed service or duty aboard, or in direct support of, a particular ship.
-
E.
usedShipsFrom
Indicates that one entity is the location or source from which used ships are sent, dispatched, or originate.
- 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_69f348de914081909fc8edff56f34dbe |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abe15d5c81909ccf4ce37f78bc43 |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aaf31a548190b2f792ff4b8c002a |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 30, 2026, 11:13 p.m.