Triple
T25863937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LNER Class A4 |
E651559
|
entity |
| Predicate | streamliningType |
P159367
|
FINISHED |
| Object | full-length streamlined casing |
—
|
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: full-length streamlined casing | Statement: [LNER Class A4, streamliningType, full-length streamlined casing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: streamliningType Context triple: [LNER Class A4, streamliningType, full-length streamlined casing]
-
A.
streamlines
Indicates that one entity makes a process, workflow, or interaction between entities more efficient, simple, or direct.
-
B.
speedupType
Indicates the kind or category of performance improvement achieved relative to a baseline.
-
C.
typeOfIntegration
Indicates the specific kind or category of integration that exists or is applied between systems, components, or processes.
-
D.
Flowline
Indicates a directed path or channel along which something (such as fluid, energy, or information) moves or is transmitted from one point to another.
-
E.
flowType
Indicates the kind or category of flow (such as direction, pattern, or mode of movement/transfer) that characterizes the relationship between entities.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6026ddccc8190a7d7cc460a5ede96 |
completed | May 2, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69f4939148dc81908706cec7d85291bc |
completed | May 1, 2026, 11:50 a.m. |
| PDg | Predicate description generation | batch_69f497b8abb88190bb672cf6907c4b8d |
completed | May 1, 2026, 12:08 p.m. |
Created at: April 22, 2026, 8:06 a.m.