Triple
T18294123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frame Relay |
E438186
|
entity |
| Predicate | usesControlProtocol |
P49579
|
FINISHED |
| Object | Local Management Interface |
—
|
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: Local Management Interface | Statement: [Frame Relay, usesControlProtocol, Local Management Interface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesControlProtocol Context triple: [Frame Relay, usesControlProtocol, Local Management Interface]
-
A.
controlProtocol
Indicates that one entity governs, regulates, or coordinates the behavior or operations of another according to a defined set of rules or procedures.
-
B.
usedControl
Indicates that one entity exercised or applied a control mechanism or method over another entity or process.
-
C.
canBeControlledFrom
Indicates that one entity has the ability or authority to operate, direct, or manage another entity remotely or indirectly.
-
D.
canControl
Indicates that one entity has the ability or authority to direct, manage, or influence the behavior or state of another entity.
-
E.
usedToControl
chosen
Indicates that one entity employed another as a means or tool to exercise control or regulation over something.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5010205bc8190a32fe731ead3d988 |
completed | April 19, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.