Triple
T12579775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venera 9 |
E300302
|
entity |
| Predicate | landerInstruments |
P37033
|
FINISHED |
| Object | thermometers |
—
|
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: thermometers | Statement: [Venera 9, landerInstruments, thermometers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landerInstruments Context triple: [Venera 9, landerInstruments, thermometers]
-
A.
instrumentsOnLander
chosen
Indicates that specific instruments are physically mounted on, attached to, or carried by a lander.
-
B.
correctedInstrument
Indicates that one entity has been adjusted, calibrated, or amended to fix errors or inaccuracies in another instrument or measurement tool.
-
C.
hostsInstrument
Indicates that one entity serves as the location, platform, or environment in which an instrument is installed, operated, or utilized.
-
D.
coreInstrument
Indicates that an instrument plays a central or primary role in performing an action or achieving an outcome.
-
E.
scientificInstruments
Indicates that one entity is a scientific instrument used by, associated with, or relevant to another entity in the context of scientific measurement or research.
- 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5 p.m.