Triple
T11146374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resourcesat-1 |
E263678
|
entity |
| Predicate | LISS-IIIResolution |
P33931
|
FINISHED |
| Object | about 23.5 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 23.5 m | Statement: [Resourcesat-1, LISS-IIIResolution, about 23.5 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: LISS-IIIResolution Context triple: [Resourcesat-1, LISS-IIIResolution, about 23.5 m]
-
A.
numberOfDrivesInLisa1
Indicates the total count of drives contained within the entity Lisa1.
-
B.
isListedBy
Indicates that one entity appears as an item or entry in a list, catalog, or register maintained or provided by another entity.
-
C.
L2Is
Indicates that one entity is located at or occupies a specific level 2 (L2) position or layer relative to another entity.
-
D.
listedWith
Indicates that an entity is included as an item or entry within a particular list, catalog, or collection.
-
E.
hasResolution
chosen
Indicates that one entity possesses, specifies, or is associated with a particular level or type of resolution (such as detail, clarity, or granularity) in relation to another entity.
- 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.