Triple
T16430820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operational Land Imager |
E399065
|
entity |
| Predicate | imagingTechnique |
P52562
|
FINISHED |
| Object | pushbroom scanning |
—
|
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: pushbroom scanning | Statement: [Operational Land Imager, imagingTechnique, pushbroom scanning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imagingTechnique Context triple: [Operational Land Imager, imagingTechnique, pushbroom scanning]
-
A.
imagingInstrument
Indicates that a particular instrument or device is used to capture or produce an image of a target or subject.
-
B.
hasImagingFinding
Indicates that an entity (typically a patient, case, or anatomical region) is associated with a specific observation or result identified through an imaging procedure (e.g., X-ray, CT, MRI).
-
C.
hasImagingType
chosen
Indicates the specific imaging modality or technique associated with or used in a given imaging procedure or result.
-
D.
imagedIn
Indicates that one entity appears within or is depicted in an image associated with another entity.
-
E.
imagedBy
Indicates that something is captured, recorded, or represented in an image created by a particular imaging device, method, or agent.
- 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.