Triple
T16257834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VMC |
E394675
|
entity |
| Predicate | observingGeometry |
P81580
|
FINISHED |
| Object | nadir viewing |
—
|
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: nadir viewing | Statement: [VMC, observingGeometry, nadir viewing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observingGeometry Context triple: [VMC, observingGeometry, nadir viewing]
-
A.
observationGeometry
chosen
Indicates the spatial and directional configuration between an observer and a target at the time an observation is made.
-
B.
observatoryFor
Indicates that something serves as an observatory specifically dedicated to observing, studying, or monitoring a particular target or subject.
-
C.
observationalVisibility
Indicates that one entity is able to observe or visually perceive another entity under given conditions.
-
D.
observatory
Indicates a relationship where a facility or structure is used to observe, monitor, or study objects or phenomena, typically in astronomy or atmospheric science.
-
E.
imagingInstrument
Indicates that a particular instrument or device is used to capture or produce an image of a target or subject.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c1fa208190995feaeba766b45f |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.