Triple
T16921243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QZSS Michibiki navigation satellites |
E410447
|
entity |
| Predicate | L6SignalUse |
P64026
|
FINISHED |
| Object | sub-meter augmentation |
—
|
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: sub-meter augmentation | Statement: [QZSS Michibiki navigation satellites, L6SignalUse, sub-meter augmentation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: L6SignalUse Context triple: [QZSS Michibiki navigation satellites, L6SignalUse, sub-meter augmentation]
-
A.
usesSignaling
Indicates that one entity communicates or coordinates with another by emitting, transmitting, or interpreting signals.
-
B.
usesSignallingPractice
Indicates that one entity employs or follows a particular signalling practice in its communication or behavior.
-
C.
songUsedAsSignalIn
Indicates that a particular song is employed as a signal or cue within a specified context, event, or system.
-
D.
usesSignalingChannel
chosen
Indicates that one entity communicates or exchanges information with another through a specific signaling channel or medium.
-
E.
signalingMode
Indicates the method or mechanism by which one entity communicates or transmits signals to another.
- 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_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. |
Created at: April 10, 2026, 5:30 a.m.