Triple
T21964060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark 3B |
E542410
|
entity |
| Predicate | hasInteriorFinish |
P5509
|
FINISHED |
| Object | British Rail corporate-era styling |
—
|
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: British Rail corporate-era styling | Statement: [Mark 3B, hasInteriorFinish, British Rail corporate-era styling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInteriorFinish Context triple: [Mark 3B, hasInteriorFinish, British Rail corporate-era styling]
-
A.
hasInteriorFeature
Indicates that an entity contains or includes a specific feature within its interior space.
-
B.
hasInteriorColor
Indicates that an entity possesses a specific color used on its interior surfaces or internal parts.
-
C.
interiorStyle
chosen
Indicates that one entity has a particular interior design style or aesthetic characterized by the other entity.
-
D.
hasRichInteriorDecoration
Indicates that an entity features elaborate, ornate, or luxuriously detailed interior decoration.
-
E.
decorativeFinish
Indicates that one entity serves as an ornamental or aesthetic surface treatment applied to 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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f12459e1848190aa8d4ccc97f434b8 |
completed | April 28, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 8:01 p.m.