Triple
T33158120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LNER Class A4 4489 Dominion of Canada |
E848641
|
entity |
| Predicate | hasStreamlinedDesign |
P199392
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [LNER Class A4 4489 Dominion of Canada, hasStreamlinedDesign, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStreamlinedDesign Context triple: [LNER Class A4 4489 Dominion of Canada, hasStreamlinedDesign, true]
-
A.
compactDesign
Indicates that something has a small, efficiently organized form or layout that minimizes space usage while maintaining functionality.
-
B.
hasDesignSide
Indicates that one entity is located on, associated with, or corresponds to a particular side or face of another entity’s design.
-
C.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
D.
hasMinimalistStyle
Indicates that something exhibits a simple, clean, and uncluttered style with minimal decorative elements.
-
E.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
- 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_69f3495b02d08190bb3d366823dffc21 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff370698ec81909bb1596d7d4112ba |
completed | May 9, 2026, 1:30 p.m. |
| PD | Predicate disambiguation | batch_69ff3699b6288190b564839cb05f5cf6 |
completed | May 9, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69ff3705e424819090ad7423ceefa506 |
completed | May 9, 2026, 1:30 p.m. |
Created at: May 1, 2026, 1:28 a.m.