Triple
T6327443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GLONASS |
E141894
|
entity |
| Predicate | userSegment |
P7221
|
FINISHED |
| Object | GNSS receivers |
—
|
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: GNSS receivers | Statement: [GLONASS, userSegment, GNSS receivers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userSegment Context triple: [GLONASS, userSegment, GNSS receivers]
-
A.
brandSegment
Indicates the specific market segment or customer group that a brand is targeted toward or associated with.
-
B.
countrySegment
Indicates that something represents a specific geographic or administrative segment or portion within a country.
-
C.
ethnicGroupUsers
Indicates that the users are associated with, belong to, or are categorized under a particular ethnic group.
-
D.
userBase
chosen
Indicates that one entity serves as the primary or foundational group of users associated with another entity.
-
E.
featuresSegment
Indicates that one entity includes or highlights a particular segment or portion of another entity as a notable part of it.
- 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_69c008d201748190917e69c41ba3f978 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064e9532081908277f10ec380a486 |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e7e2d48190af9d004236466788 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:29 p.m.