Triple
T17046041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landsat 7 |
E413569
|
entity |
| Predicate | onboardRecorder |
P125630
|
FINISHED |
| Object | solid-state recorder |
—
|
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: solid-state recorder | Statement: [Landsat 7, onboardRecorder, solid-state recorder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: onboardRecorder Context triple: [Landsat 7, onboardRecorder, solid-state recorder]
-
A.
hasVoiceRecorder
Indicates that one entity possesses or is equipped with a voice recording device or capability in relation to another entity or context.
-
B.
recordingMode
Indicates the method or configuration by which something is recorded, such as how data, audio, or video capture is performed.
-
C.
includesLiveRecordingFrom
Indicates that something contains or incorporates a live recording sourced from another entity.
-
D.
recordingOf
Indicates that one entity is an audio or video capture or performance that documents, represents, or preserves another entity (such as a work, event, or expression).
-
E.
usedForRecordingBy
Indicates that something serves as a medium, tool, or device that is employed by an agent to make a recording.
- 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.