Triple
T21228445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PS-1 boxcar |
E523141
|
entity |
| Predicate | hasSideConstruction |
P38699
|
FINISHED |
| Object | steel sides |
—
|
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: steel sides | Statement: [PS-1 boxcar, hasSideConstruction, steel sides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSideConstruction Context triple: [PS-1 boxcar, hasSideConstruction, steel sides]
-
A.
hasTopConstruction
Indicates that one entity serves as the uppermost structural element or construction positioned on top of another entity.
-
B.
hasConstruction
chosen
Indicates that one entity possesses, contains, or is characterized by a particular construction, structure, or built form associated with it.
-
C.
hasSideWalls
Indicates that an object or structure possesses side walls as part of its physical configuration.
-
D.
hasSideArch
Indicates that one entity possesses or features a secondary or lateral arch structure in relation to another entity.
-
E.
hasBside
Indicates that one item serves as the B-side counterpart or secondary track associated with another primary item, typically in a recording or media release.
- 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_69e0b512ad94819087942b2ed925185f |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734ad5068819088b203eeba4e6380 |
completed | April 21, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e5f60e1a888190ba75e2e900270a4e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:44 p.m.