Triple
T11157314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leander class |
E263943
|
entity |
| Predicate | ship |
P880
|
FINISHED |
| Object | HMS Ajax |
E52191
|
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 Ajax | Statement: [Leander class, ship, HMS Ajax]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HMS Ajax Context triple: [Leander class, ship, HMS Ajax]
-
A.
HMS Ajax
HMS Ajax was a British Royal Navy warship that served as part of the King George V-class of battleships during the mid-20th century.
-
B.
HMS Ajax
chosen
HMS Ajax was a British Leander-class light cruiser of the Royal Navy that gained fame for its role in early World War II naval actions, particularly in the South Atlantic.
-
C.
HMS Valiant
HMS Valiant was a British Royal Navy nuclear-powered fleet submarine of the Valiant class that served during the Cold War.
-
D.
HMS Valiant
HMS Valiant is a planned Royal Navy nuclear-powered ballistic missile submarine intended to serve as part of the United Kingdom’s next-generation strategic deterrent force.
-
E.
HMS Indefatigable
HMS Indefatigable was a British battlecruiser of the early 20th century Royal Navy, best known for her catastrophic loss during the First World War.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e87fe9a881909540ecc4ed9b6b9f |
completed | April 9, 2026, 5:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e712e6288481908071e248a50209e0 |
completed | April 21, 2026, 6:02 a.m. |
Created at: April 8, 2026, 9:28 p.m.