Triple
T36709860
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WiFS |
E906765
|
entity |
| Predicate | groundSamplingDistance |
P68593
|
FINISHED |
| Object | approximately 188 m |
—
|
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: approximately 188 m | Statement: [WiFS, groundSamplingDistance, approximately 188 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groundSamplingDistance Context triple: [WiFS, groundSamplingDistance, approximately 188 m]
-
A.
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.
-
B.
samplingResolution
chosen
Indicates the level of detail or granularity at which data is sampled or measurements are taken in a process or system.
-
C.
elevationAccuracy
Indicates the degree of precision or reliability associated with a measured or reported elevation value in the relationship.
-
D.
depthApprox
Indicates an approximate or estimated depth relationship between entities, rather than an exact measured depth.
-
E.
typicalHorizontalAccuracy
Indicates the usual or expected degree of precision in the horizontal (x–y) position of a measurement or location estimate.
- 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:12 p.m.