Triple
T11146375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resourcesat-1 |
E263678
|
entity |
| Predicate | AWiFSResolution |
P25684
|
FINISHED |
| Object | about 56 m |
—
|
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 56 m | Statement: [Resourcesat-1, AWiFSResolution, about 56 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AWiFSResolution Context triple: [Resourcesat-1, AWiFSResolution, about 56 m]
-
A.
targetResolution
Indicates the specific resolution or level of detail that an action, process, or system is intended to achieve or operate at.
-
B.
sensorResolution
Indicates the level of detail or precision with which a sensor can measure or distinguish changes in the observed quantity or environment.
-
C.
samplingResolution
Indicates the level of detail or granularity at which data is sampled or measurements are taken in a process or system.
-
D.
hasSpatialResolution
chosen
Indicates that something is characterized by a specific level of spatial detail or granularity at which it can represent or distinguish features in space.
-
E.
typicalResolution
Indicates the usual or standard level of detail or clarity at which something (such as an image, display, or representation) is normally rendered or presented.
- 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.