Triple
T3787239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIL-STD-1553 databus |
E85556
|
entity |
| Predicate | supportsMultipleTerminals |
P51516
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [MIL-STD-1553 databus, supportsMultipleTerminals, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsMultipleTerminals Context triple: [MIL-STD-1553 databus, supportsMultipleTerminals, true]
-
A.
supportsMultipleWindows
Indicates that the subject can handle or display more than one window or view simultaneously.
-
B.
supportsDeviceCount
Indicates the number of devices that a system, service, or component is capable of supporting concurrently.
-
C.
numberOfTerminals
Indicates the total count of terminal points or endpoints associated with an entity.
-
D.
supportsMultiuser
Indicates that the subject is capable of handling or enabling simultaneous use by multiple users.
-
E.
hasIntegratedTerminal
Indicates that one entity includes or supports a built-in terminal interface as part of its functionality.
- 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_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. |
| PDg | Predicate description generation | batch_69aee633dab88190b14cec8afb19ca6a |
completed | March 9, 2026, 3:24 p.m. |
Created at: March 9, 2026, 3:13 p.m.