Triple
T11001727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NavIC satellites |
E260017
|
entity |
| Predicate | targetUserSegments |
P481
|
FINISHED |
| Object | civilian users |
—
|
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: civilian users | Statement: [NavIC satellites, targetUserSegments, civilian users]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetUserSegments Context triple: [NavIC satellites, targetUserSegments, civilian users]
-
A.
targetMarket
chosen
Indicates the group of consumers or organizations that a product, service, or campaign is specifically intended and designed to reach.
-
B.
targetsGroup
Indicates that an action, influence, or effect is directed toward a specific group as its intended recipient or focus.
-
C.
targetsUseCase
Indicates that one entity is aimed at or designed to address a particular use case associated with another entity.
-
D.
passengerSegments
Indicates a relationship where a journey or trip is divided into distinct legs or segments that a passenger travels through.
-
E.
targetUserActivity
Indicates that a specific user is the intended recipient or focus of a particular activity or action.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d796d760008190930228fa77b61b8b |
completed | April 9, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69d72e96be6c8190a46c69f61b2d8cd4 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.