Triple
T32750351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SACLOS |
E837477
|
entity |
| Predicate | commandTransmission |
P148774
|
FINISHED |
| Object | wire |
—
|
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: wire | Statement: [SACLOS, commandTransmission, wire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandTransmission Context triple: [SACLOS, commandTransmission, wire]
-
A.
commandsThrough
Indicates that one entity exercises authority or control over another indirectly, acting through an intermediary or chain of command.
-
B.
baseTransmission
Indicates the fundamental or default mode by which something is transmitted or passed from one entity to another.
-
C.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
D.
commandReceived
Indicates that an entity has successfully received a command issued by another entity or system.
-
E.
transmitsVia
chosen
Indicates that something is conveyed, sent, or carried from one entity to another through a specified medium, channel, or mechanism.
- 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_69f34937f97c8190b7f84bea045df3ae |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 1, 2026, 1:12 a.m.