Triple
T23736748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsiklon navigation system |
E586559
|
entity |
| Predicate | usedSignalType |
P4618
|
FINISHED |
| Object | radio signals |
—
|
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 signals | Statement: [Tsiklon navigation system, usedSignalType, radio signals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedSignalType Context triple: [Tsiklon navigation system, usedSignalType, radio signals]
-
A.
signalType
chosen
Indicates the specific kind or category of signal associated with or used by an entity or interaction.
-
B.
usesSignaling
Indicates that one entity communicates or coordinates with another by emitting, transmitting, or interpreting signals.
-
C.
detectsSignalType
Indicates that an entity identifies or recognizes the specific type or category of a given signal.
-
D.
transportsSignalType
Indicates that one entity carries or conveys a particular type of signal from one point to another.
-
E.
usesSignallingPractice
Indicates that one entity employs or follows a particular signalling practice in its communication or behavior.
- 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_69f1bad28fa481909d7a6a6e98a7b0a5 |
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.