Triple
T31507402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trident successor programme |
E803854
|
entity |
| Predicate | otherPlannedBoats |
P178832
|
FINISHED |
| Object | HMS Valiant |
—
|
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 Valiant | Statement: [Trident successor programme, otherPlannedBoats, HMS Valiant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: otherPlannedBoats Context triple: [Trident successor programme, otherPlannedBoats, HMS Valiant]
-
A.
numberOfPlannedShips
Indicates the total count of ships that are intended or scheduled to be built, deployed, or used according to a plan.
-
B.
shipDraft
Indicates the depth of a ship’s hull below the waterline, typically representing how deeply the vessel sits in the water.
-
C.
laterShipType
Indicates that one ship type chronologically succeeds or is introduced after another ship type.
-
D.
shipbuildingActivity
Indicates the activity or process of constructing, assembling, or significantly modifying ships or large watercraft.
-
E.
seventhBoat
Indicates that an entity is identified specifically as the seventh boat in an ordered sequence or group of boats.
- 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_69f348ceb0a48190ae7feca263b6296c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71421e8d08190807ccfb15d0f0ddb |
completed | May 3, 2026, 9:23 a.m. |
Created at: April 30, 2026, 9:48 p.m.