Triple
T17046043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landsat 7 |
E413569
|
entity |
| Predicate | scanLineCorrectorIssue |
P125632
|
FINISHED |
| Object | causes data gaps in imagery |
—
|
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: causes data gaps in imagery | Statement: [Landsat 7, scanLineCorrectorIssue, causes data gaps in imagery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scanLineCorrectorIssue Context triple: [Landsat 7, scanLineCorrectorIssue, causes data gaps in imagery]
-
A.
aberrationCorrection
Indicates the application or presence of a process that corrects optical or imaging aberrations in a system or setup.
-
B.
lineCorridor
Indicates that one entity is a corridor represented or approximated by a line, typically modeling a narrow passageway or path between areas.
-
C.
requiresCorrection
Indicates that something is identified as needing modification, adjustment, or fixing to correct an error or deficiency.
-
D.
usesForwardErrorCorrection
Indicates that one entity applies forward error correction techniques to detect and correct errors in data transmitted to or received from another entity.
-
E.
lineReplaced
Indicates that one line has been substituted or superseded by another line, typically in a versioning, editing, or modification context.
- 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_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. |
| PDg | Predicate description generation | batch_69e3753f93c88190808fec5692f66699 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:33 a.m.