Triple
T11001723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NavIC satellites |
E260017
|
entity |
| Predicate | navigationSignals |
P96945
|
FINISHED |
| Object | L5 band |
—
|
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: L5 band | Statement: [NavIC satellites, navigationSignals, L5 band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationSignals Context triple: [NavIC satellites, navigationSignals, L5 band]
-
A.
navigation
Indicates the act or process of determining and following a path or route from one location or state to another.
-
B.
navigationSignificance
Indicates the degree to which something serves as a meaningful aid or reference point for determining or following a route or direction.
-
C.
navigationFrom
Indicates a directional navigation relationship where movement or guidance starts from a specified source location or point.
-
D.
navigationArea
Indicates that a specified region or space is designated for movement, routing, or pathfinding within an environment.
-
E.
navigationNote
Indicates that there is an auxiliary note or instruction intended to guide or assist navigation within a resource, interface, or environment.
- 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_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. |
| PDg | Predicate description generation | batch_69d733b27ffc81908ab1b8df198cd5c7 |
completed | April 9, 2026, 5:05 a.m. |
Created at: April 8, 2026, 9:25 p.m.