Triple
T21228435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PS-1 boxcar |
E523141
|
entity |
| Predicate | hasCouplerType |
P21783
|
FINISHED |
| Object | Janney (AAR) knuckle couplers |
—
|
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: Janney (AAR) knuckle couplers | Statement: [PS-1 boxcar, hasCouplerType, Janney (AAR) knuckle couplers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCouplerType Context triple: [PS-1 boxcar, hasCouplerType, Janney (AAR) knuckle couplers]
-
A.
hasCouplers
chosen
Indicates that one entity is equipped with or possesses couplers that enable it to connect or link to another entity.
-
B.
hasCoupling
Indicates that two entities are linked or joined together in a way that allows them to interact, transfer, or coordinate motion, energy, or information.
-
C.
hasCouplingConstant
Indicates that one entity is associated with a specific coupling constant value that quantifies the strength of an interaction or relationship.
-
D.
hasConnector
Indicates that one entity is linked or joined to another entity through a connector or connecting element.
-
E.
hasBondType
Indicates the specific kind of bond or connection that exists between two related entities.
- 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.