Triple
T7804428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MQ-1 Predator |
E180511
|
entity |
| Predicate | dataLink |
P20417
|
FINISHED |
| Object | line-of-sight communications |
—
|
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: line-of-sight communications | Statement: [MQ-1 Predator, dataLink, line-of-sight communications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataLink Context triple: [MQ-1 Predator, dataLink, line-of-sight communications]
-
A.
linkLayer
Indicates a relationship where one entity is connected to another at the data link (Layer 2) level of a network stack, enabling direct frame-level communication between them.
-
B.
linkedNetwork
Indicates that two entities are connected through a shared or associated network relationship.
-
C.
dataInterface
Indicates that one entity serves as a data interface through which another entity can access, exchange, or manipulate data.
-
D.
subLayerInDataLinkLayer
Indicates that one protocol or component functions as a subordinate or encapsulated sublayer within another protocol or component in the data link layer of a network stack.
-
E.
linkType
chosen
Indicates the specific kind or category of relationship that connects two linked entities.
- 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_69ca827e50cc8190a92a733577184938 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae9111b2481909684a2d4aa4831c2 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:34 p.m.