Triple
T16430624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USGS EarthExplorer |
E399061
|
entity |
| Predicate | supportsBulkDownload |
P79779
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [USGS EarthExplorer, supportsBulkDownload, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBulkDownload Context triple: [USGS EarthExplorer, supportsBulkDownload, yes]
-
A.
supportsDigitalDownloads
chosen
Indicates that one entity enables or allows the other entity to provide or access digital file downloads.
-
B.
supportsBackingFiles
Indicates that an entity is capable of using or relying on underlying backing files to store or manage its data or state.
-
C.
supportsBatchProcessing
Indicates that the subject can handle multiple items or tasks in a single grouped operation rather than processing them individually.
-
D.
supportsAttachments
Indicates that the subject is capable of handling or allowing the inclusion of file or data attachments in its operation or context.
-
E.
supportsImportExport
Indicates that one entity provides functionality for importing and exporting data or resources to and from 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328fe0f488190ac34aa677c980a20 |
completed | April 18, 2026, 6:47 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.