Triple
T20658974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EMD SD40-2 |
E507704
|
entity |
| Predicate | controlStand |
P140950
|
FINISHED |
| Object | EMD standard control stand |
—
|
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: EMD standard control stand | Statement: [EMD SD40-2, controlStand, EMD standard control stand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlStand Context triple: [EMD SD40-2, controlStand, EMD standard control stand]
-
A.
controlStatus
Indicates that one entity has a particular level, state, or condition of control over another entity or process.
-
B.
controlsSystem
Indicates that one entity has the authority or capability to direct, manage, or regulate the operation of a system.
-
C.
exportControl
Indicates that an entity is subject to rules or restrictions governing the transfer or export of goods, services, or information across borders.
-
D.
controlsWith
Indicates that one entity exercises authority, direction, or regulatory power over another entity through specific means or mechanisms.
-
E.
controlFrom
Indicates that one entity exercises authority, influence, or regulatory power over another entity or process.
- 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b2eefd5c8190a71d4be690a6ae0e |
completed | April 20, 2026, 11:12 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 11:43 a.m.