Triple
T17046046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landsat 7 |
E413569
|
entity |
| Predicate | imageryFormat |
P38824
|
FINISHED |
| Object | Level-1 terrain-corrected products |
—
|
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: Level-1 terrain-corrected products | Statement: [Landsat 7, imageryFormat, Level-1 terrain-corrected products]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imageryFormat Context triple: [Landsat 7, imageryFormat, Level-1 terrain-corrected products]
-
A.
typicalPictureFormat
Indicates the standard or most commonly used picture format associated with an entity (such as a device, medium, or context).
-
B.
sensorFormat
Indicates the data encoding or representation standard used by a sensor to output its measurements.
-
C.
preservationFormat
Indicates the format or encoding in which something is maintained specifically for long-term preservation.
-
D.
formerPictureFormat
Indicates that an entity previously used a particular picture format before changing to a different one.
-
E.
operatesInFormat
chosen
Indicates that an entity functions, performs its role, or is carried out using a specified format.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3da9e3d8881909f197aba0e4c97e7 |
completed | April 18, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.