Triple
T3787221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIL-STD-1553 databus |
E85556
|
entity |
| Predicate | busControllerRole |
P5994
|
FINISHED |
| Object | initiates all message transfers |
—
|
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: initiates all message transfers | Statement: [MIL-STD-1553 databus, busControllerRole, initiates all message transfers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: busControllerRole Context triple: [MIL-STD-1553 databus, busControllerRole, initiates all message transfers]
-
A.
roleOfDevice
Indicates that a device participates in a situation or system with a specified functional role or purpose.
-
B.
hardwareRole
Indicates the functional role or purpose that a piece of hardware serves within a system or configuration.
-
C.
hasBusArbitration
chosen
Indicates that one entity manages or participates in the control and coordination of access to a shared communication bus among multiple entities.
-
D.
systemRole
Indicates the functional position or responsibility that an entity holds within a larger system or structure.
-
E.
roleInAttitudeControl
Indicates that an entity has a specific function or responsibility within an attitude control process or system.
- 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_69aed937fa8881908208ef3801060826 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee634c6ac819099653c660c286746 |
completed | March 9, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69aee3d3c92c819081d9d5c45ef37a5d |
completed | March 9, 2026, 3:14 p.m. |
Created at: March 9, 2026, 3:13 p.m.