Triple
T16921227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QZSS Michibiki navigation satellites |
E410447
|
entity |
| Predicate | augmentationSystemType |
P96689
|
FINISHED |
| Object | SBAS-like |
—
|
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: SBAS-like | Statement: [QZSS Michibiki navigation satellites, augmentationSystemType, SBAS-like]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: augmentationSystemType Context triple: [QZSS Michibiki navigation satellites, augmentationSystemType, SBAS-like]
-
A.
canBeAugmentedWith
Indicates that one entity is capable of being enhanced, expanded, or supplemented by another entity.
-
B.
extensionType
chosen
Indicates the specific kind or category of extension that characterizes how something is extended or augmented beyond its base form.
-
C.
systemTypeOperated
Indicates that an entity operates, controls, or runs a particular type of system.
-
D.
adjustmentType
Indicates the specific kind or category of modification applied to an existing value, state, or configuration within the relationship.
-
E.
establishedSystem
Indicates that an entity has created, set up, or formally put into operation a particular system or structured arrangement.
- 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.