Triple
T31225567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Dreadnought |
E796123
|
entity |
| Predicate | designLedBy |
P28525
|
FINISHED |
| Object | Admiral Sir John Fisher |
—
|
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: Admiral Sir John Fisher | Statement: [HMS Dreadnought, designLedBy, Admiral Sir John Fisher]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designLedBy Context triple: [HMS Dreadnought, designLedBy, Admiral Sir John Fisher]
-
A.
designLead
chosen
Indicates that one entity serves as the primary designer or person in charge of leading the design work for another entity or project.
-
B.
designSucceededBy
Indicates that one design is followed or replaced by another design in a temporal or version sequence.
-
C.
designedBy
Indicates that one entity is the creator, planner, or architect responsible for the form or structure of another entity.
-
D.
developmentLedBy
Indicates that the development of something is directed, managed, or overseen by a particular agent or entity.
-
E.
designSelectedIn
Indicates that a particular design has been chosen or picked out within a specific context, set, or selection process.
- F. None of above.
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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: April 29, 2026, 9:10 p.m.