Triple
T33980929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daring-class destroyer |
E871279
|
entity |
| Predicate | firstRoyalNavyShipCompleted |
P34263
|
FINISHED |
| Object | HMS Daring |
E820509
|
NE 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: HMS Daring | Statement: [Daring-class destroyer, firstRoyalNavyShipCompleted, HMS Daring]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstRoyalNavyShipCompleted Context triple: [Daring-class destroyer, firstRoyalNavyShipCompleted, HMS Daring]
-
A.
BritishShipRate
Indicates that the subject is classified or rated according to the British naval ship rating system (e.g., first-rate, second-rate, etc.).
-
B.
firstShip
chosen
Indicates that the subject is the earliest or initial ship associated with, created by, or used in relation to the object.
-
C.
BritishShipArmamentApproximate
Indicates that a British ship’s armament is specified in approximate rather than exact terms.
-
D.
hullConstructedIn
Indicates that the hull of an object (such as a ship or vessel) was built or constructed at a specific location or facility.
-
E.
originalShipLaunchedIn
Indicates that an original ship was first launched in a specified year, place, or context.
- F. None of above.
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_69f3499da0188190ab1a4ff06fb06a2a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39cfac0f0081909ea94851419ad716 |
completed | June 23, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:50 a.m.