Triple
T15702008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kensington (Olympia) railway station |
E380614
|
entity |
| Predicate | hasIbstockStyle |
P93228
|
FINISHED |
| Object | Victorian architecture |
—
|
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: Victorian architecture | Statement: [Kensington (Olympia) railway station, hasIbstockStyle, Victorian architecture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIbstockStyle Context triple: [Kensington (Olympia) railway station, hasIbstockStyle, Victorian architecture]
-
A.
hasIbstockCode
Indicates that an entity is associated with a specific Ibstock identification code.
-
B.
hasStockSeries
Indicates that an entity is associated with a particular stock time series or sequence of stock-related data.
-
C.
hasISIN
Indicates that a financial instrument is associated with a specific International Securities Identification Number (ISIN) that uniquely identifies it.
-
D.
hasStationStyle
chosen
Indicates that one entity (typically a station) possesses or is characterized by a particular architectural or design style.
-
E.
hasContractStyle
Indicates that one entity is associated with or characterized by a particular contract style or contractual format.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0051d639481909a10614e8f83e659 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:45 a.m.