Triple
T32508269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaofen-3 |
E830858
|
entity |
| Predicate | imagingCondition |
P38871
|
FINISHED |
| Object | cloud-penetrating |
—
|
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: cloud-penetrating | Statement: [Gaofen-3, imagingCondition, cloud-penetrating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imagingCondition Context triple: [Gaofen-3, imagingCondition, cloud-penetrating]
-
A.
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).
-
B.
imagingActivation
Indicates that an entity initiates or undergoes an activation process related to imaging or image-based functionality.
-
C.
imagedIn
Indicates that one entity appears within or is depicted in an image associated with another entity.
-
D.
hasImagingType
Indicates the specific imaging modality or technique associated with or used in a given imaging procedure or result.
-
E.
imagedBy
chosen
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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c44d21648190ada905d52e251b1f |
completed | May 3, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1 a.m.