Triple
T17046042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landsat 7 |
E413569
|
entity |
| Predicate | scanLineCorrectorFailureDate |
P125631
|
FINISHED |
| Object | 2003-05-31 |
—
|
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: 2003-05-31 | Statement: [Landsat 7, scanLineCorrectorFailureDate, 2003-05-31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scanLineCorrectorFailureDate Context triple: [Landsat 7, scanLineCorrectorFailureDate, 2003-05-31]
-
A.
immediateCauseDate
Indicates the specific date on which an event or condition directly caused another event or outcome to occur.
-
B.
hasCaptureDate
Indicates the date on which something (such as an image, video, or data sample) was originally captured or recorded.
-
C.
rescueDate
Indicates the date on which a rescue action or operation took place.
-
D.
includesCorrectionsFor
Indicates that one item contains modifications, fixes, or amendments that address errors or issues present in another item.
-
E.
completionDateMainLine
Indicates the date on which the primary or main phase of an activity, project, or process is completed.
- 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_69e3da9d7e988190a5e3991c7123f9b0 |
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.