Triple
T19214936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venera 6 |
E480456
|
entity |
| Predicate | atmosphericProbe |
P135006
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Venera 6, atmosphericProbe, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: atmosphericProbe Context triple: [Venera 6, atmosphericProbe, yes]
-
A.
atmosphericEntry
Indicates the event of an object transitioning from space into a planetary atmosphere, experiencing aerodynamic forces and heating as it descends.
-
B.
usesAtmosphereOf
Indicates that one entity makes use of or operates within the atmospheric conditions or composition associated with another entity.
-
C.
hasAtmosphere
Indicates that an astronomical body possesses a surrounding layer of gases held by its gravity.
-
D.
hasGeneralAtmosphere
Indicates that one entity is characterized by or associated with a particular overall mood, tone, or ambient quality provided by another entity.
-
E.
hasAtmosphericFeature
Indicates that one entity possesses or exhibits a particular feature or characteristic of its atmosphere.
- 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_69d8e8cb8c348190b52075823911c869 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa397c188190b85bcfd9afd8dce6 |
completed | April 20, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69e4dcf22b3c8190bee02e3af946e114 |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:22 p.m.