Triple
T29953638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LNER Class K3 |
E760835
|
entity |
| Predicate | hasDesignerTitle |
P75519
|
FINISHED |
| Object | Sir |
—
|
LITERAL 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: Sir | Statement: [LNER Class K3, hasDesignerTitle, Sir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDesignerTitle Context triple: [LNER Class K3, hasDesignerTitle, Sir]
-
A.
hasOpeningTitleDesignBy
Indicates that an entity’s opening title sequence was designed or created by a specified designer or design entity.
-
B.
hasTitleCardDesign
Indicates that one entity is responsible for or associated with the design of the title card of another entity.
-
C.
hasAuthorTitle
chosen
Indicates that an author holds or is designated by a specific title (e.g., professional, honorific, or role-based).
-
D.
hasDesignation
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
E.
hasDesignAuthority
Indicates that one entity holds the recognized power or responsibility to make or approve design decisions affecting another entity.
- 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: April 29, 2026, 6:26 p.m.