Triple
T37140102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SRTM |
E920081
|
entity |
| Predicate | repeatCoverage |
P187185
|
FINISHED |
| Object | single-pass interferometry |
—
|
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: single-pass interferometry | Statement: [SRTM, repeatCoverage, single-pass interferometry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repeatCoverage Context triple: [SRTM, repeatCoverage, single-pass interferometry]
-
A.
coverageBasis
Indicates the underlying principle, rule, or criteria on which a particular coverage or protection is determined or applied.
-
B.
cobertura
Indicates that one entity provides coverage, protection, or a covering layer over another entity.
-
C.
segmentCovered
Indicates that one segment or portion of something is fully or partially covered or spanned by another.
-
D.
stageCoverage
Indicates that one entity provides or has coverage, representation, or support for another within a particular stage or phase of a process or workflow.
-
E.
edgeCoverage
Indicates that one element (such as a test, path, or configuration) covers or exercises a specific edge or connection in a graph or network structure.
- 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_69f76e9e9d008190a250b0387c992c74 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
| PDg | Predicate description generation | batch_69fb344ba5408190a6fe8face293d88b |
completed | May 6, 2026, 12:30 p.m. |
Created at: May 3, 2026, 4:15 p.m.