Triple
T969820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DE30AC locomotive |
E20919
|
entity |
| Predicate | hasCoupling |
P22536
|
FINISHED |
| Object | AAR knuckle coupler |
—
|
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: AAR knuckle coupler | Statement: [DE30AC locomotive, hasCoupling, AAR knuckle coupler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoupling Context triple: [DE30AC locomotive, hasCoupling, AAR knuckle coupler]
-
A.
couplingCapability
Indicates the ability or suitability of one entity to connect, link, or interface with another in a functional or compatible manner.
-
B.
doesNotCoupleTo
Indicates that one entity does not form a functional or physical coupling or interaction with another entity.
-
C.
hasComb
Indicates that an entity possesses or is equipped with a comb.
-
D.
hasPart
Indicates that one entity is a component, segment, or constituent part of another entity.
-
E.
hasCorrelativesSystem
Indicates that one entity possesses or employs a system of correlatives—structured, corresponding elements or forms that are systematically related to each other.
- 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b4497d688190b59c3a195e377080 |
completed | March 1, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a579888190afb489ac9fe8391c |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b385176081909e3e8c3f647c1fd4 |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:40 p.m.