Triple
T16921238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QZSS Michibiki navigation satellites |
E410447
|
entity |
| Predicate | providesSignal |
P124740
|
FINISHED |
| Object | L1 C/A |
—
|
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: L1 C/A | Statement: [QZSS Michibiki navigation satellites, providesSignal, L1 C/A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesSignal Context triple: [QZSS Michibiki navigation satellites, providesSignal, L1 C/A]
-
A.
definesOptionalSignal
Indicates that an entity specifies a signal that is not mandatory and may or may not be present or used.
-
B.
signaled
Indicates that one entity communicated a message, warning, or instruction to another through a deliberate signal or cue.
-
C.
sentSignalTo
Indicates that one entity transmitted a signal or message to another entity.
-
D.
usesSignaling
Indicates that one entity communicates or coordinates with another by emitting, transmitting, or interpreting signals.
-
E.
sentSignalFrom
Indicates that one entity transmitted or emitted a signal originating from a specified source entity.
- F. None of above. chosen
Provenance (4 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cdee252c81908621b2ca897416e9 |
completed | April 18, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e32d7aae948190bc238d765795688c |
completed | April 18, 2026, 7:06 a.m. |
Created at: April 10, 2026, 5:30 a.m.