Triple
T30713317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNCB Class 18 |
E781951
|
entity |
| Predicate | bufferType |
P170056
|
FINISHED |
| Object | side buffers |
—
|
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: side buffers | Statement: [SNCB Class 18, bufferType, side buffers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bufferType Context triple: [SNCB Class 18, bufferType, side buffers]
-
A.
buffType
Indicates the type or category of beneficial or detrimental status effect applied to an entity.
-
B.
bufferRole
Indicates that an entity serves as an intermediary or protective layer between other entities, moderating or absorbing effects, interactions, or changes.
-
C.
binaryType
Indicates that something is classified as a binary type, typically distinguishing between two mutually exclusive categories or values.
-
D.
bufferZone
Indicates the existence of an area or region that serves as a protective or separating space between two or more entities or activities.
-
E.
blockType
Indicates that one entity is classified as a specific type or category of block in relation to 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_69f224acd24481908ed5f96f0d69b5dd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68c1fd1e081908fa0a55e82f3030b |
completed | May 2, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69f688034580819086a0f9100645f8ba |
completed | May 2, 2026, 11:25 p.m. |
Created at: April 29, 2026, 8:35 p.m.