Triple
T8489115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intergalactic Radio Station |
E200914
|
entity |
| Predicate | usesSignalType |
P4618
|
FINISHED |
| Object | radio signal |
—
|
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 signal | Statement: [Intergalactic Radio Station, usesSignalType, radio signal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSignalType Context triple: [Intergalactic Radio Station, usesSignalType, radio signal]
-
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.
searchesSignalType
Indicates that an entity actively looks for or queries a specific type or category of signal.
-
D.
usesSignallingPractice
Indicates that one entity employs or follows a particular signalling practice in its communication or behavior.
-
E.
usesSignalingChannel
Indicates that one entity communicates or exchanges information with another through a specific signaling channel or medium.
- 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe5581d308190b47d76dd49a36529 |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:13 p.m.