Triple
T23737362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTK |
E586573
|
entity |
| Predicate | requiresCommunicationChannel |
P127291
|
FINISHED |
| Object | radio link |
—
|
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: radio link | Statement: [RTK, requiresCommunicationChannel, radio link]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresCommunicationChannel Context triple: [RTK, requiresCommunicationChannel, radio link]
-
A.
requiresChannel
chosen
Indicates that an entity or action depends on or must be associated with a specific communication or distribution channel in order to occur or be valid.
-
B.
communicationRequirement
Indicates that one entity is obligated or expected to communicate with another entity under specified conditions or for a particular purpose.
-
C.
hasCommunicationAccess
Indicates that one entity is able to communicate with, or use a communication channel or service provided by, another entity.
-
D.
usedToCommunicate
Indicates that one entity serves as a medium or tool through which another entity conveys information, messages, or signals.
-
E.
communicationChannel
Indicates a medium or method through which information is transmitted between parties.
- 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad356c88190ae29ce403145ee73 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:10 p.m.