Triple
T13286456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barons Court station |
E316456
|
entity |
| Predicate | hasBrickwork |
P38699
|
FINISHED |
| Object | distinctive red brick station building |
—
|
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: distinctive red brick station building | Statement: [Barons Court station, hasBrickwork, distinctive red brick station building]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBrickwork Context triple: [Barons Court station, hasBrickwork, distinctive red brick station building]
-
A.
numberOfBricksUsed
Indicates the quantity of bricks that were utilized in constructing or forming something.
-
B.
hasConstruction
chosen
Indicates that one entity possesses, contains, or is characterized by a particular construction, structure, or built form associated with it.
-
C.
brickTypeUsedFor
Indicates that a particular type of brick is used for constructing or forming a specified object, structure, or component.
-
D.
hasWallsMaterial
Indicates that the material specified is used to construct or cover the walls of the referenced entity.
-
E.
hasCloisterWalls
Indicates that something possesses or is surrounded by cloister walls as an architectural feature.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:27 p.m.