Triple
T11146190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRS-1C |
E263674
|
entity |
| Predicate | WiFSSwathWidth |
P81986
|
FINISHED |
| Object | about 810 kilometres |
—
|
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: about 810 kilometres | Statement: [IRS-1C, WiFSSwathWidth, about 810 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: WiFSSwathWidth Context triple: [IRS-1C, WiFSSwathWidth, about 810 kilometres]
-
A.
swathWidth
chosen
Indicates the lateral extent or breadth covered by an action or effect, typically measured as the width of the area impacted or traversed.
-
B.
swathWidthRange
Indicates the range of possible widths covered or affected in a single pass or sweep of an action or process.
-
C.
maximumChannelWidth
Indicates the greatest allowable or observed width of a channel in the given context.
-
D.
supportsWiFiStandard
Indicates that one entity is compatible with and able to operate using a specified Wi-Fi communication standard defined by another entity.
-
E.
observingBand
Indicates that an entity is observing or monitoring another entity using a specific spectral band or frequency range.
- 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_69d6aa9ccddc8190868998c8b7beb060 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e86e9ef48190b4df4b14319a954f |
completed | April 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69d75ce104908190b6cc31ef2f67846a |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:28 p.m.