Triple
T3918692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landsat satellites |
E88905
|
entity |
| Predicate | hasSwathWidth |
P3989
|
FINISHED |
| Object | about 185 kilometers |
—
|
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: about 185 kilometers | Statement: [Landsat satellites, hasSwathWidth, about 185 kilometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSwathWidth Context triple: [Landsat satellites, hasSwathWidth, about 185 kilometers]
-
A.
swathWidthRange
Indicates the range of possible widths covered or affected in a single pass or sweep of an action or process.
-
B.
hasWidth
chosen
Indicates that an entity possesses a specific measurement or extent along its width dimension.
-
C.
maximumChannelWidth
Indicates the greatest allowable or observed width of a channel in the given context.
-
D.
typicalWidth
Indicates the usual or characteristic width associated with an entity, as opposed to an exact or measured width in a specific instance.
-
E.
hasSpatialResolution
Indicates that something is characterized by a specific level of spatial detail or granularity at which it can represent or distinguish features in space.
- 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_69aed955229881909e85e73ffab1d343 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef188b474819087680db42b04ecdd |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee75eedcc81908088ff4dbb8be56b |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.