Triple
T31224811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cold War-era Royal Navy |
E796108
|
entity |
| Predicate | notableDestroyerClass |
P160232
|
FINISHED |
| Object | County-class destroyer |
E258335
|
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: County-class destroyer | Statement: [Cold War-era Royal Navy, notableDestroyerClass, County-class destroyer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDestroyerClass Context triple: [Cold War-era Royal Navy, notableDestroyerClass, County-class destroyer]
-
A.
notableShip
Indicates that there is a notable or significant ship associated with the subject entity.
-
B.
shipClassDeveloped
chosen
Indicates that a particular ship class was developed or designed by a specified entity (such as a country, organization, or manufacturer).
-
C.
notableVictimShip
Indicates that a ship is recognized as a particularly significant or noteworthy victim in a specific incident or context.
-
D.
shipClass
Indicates the classification or type category to which a particular ship belongs.
-
E.
plannedArmamentClass
Indicates that an entity is intended or designated to be equipped with a particular class or type of armament.
- 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a295932676c81909e15816aa9db36ff |
completed | June 10, 2026, 12:31 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:10 p.m.