Triple
T20047969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venera 15 |
E497611
|
entity |
| Predicate | imagedSurfaceFeature |
P47694
|
FINISHED |
| Object | Venusian plains |
—
|
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: Venusian plains | Statement: [Venera 15, imagedSurfaceFeature, Venusian plains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: imagedSurfaceFeature Context triple: [Venera 15, imagedSurfaceFeature, Venusian plains]
-
A.
surfaceFeatureOf
chosen
Indicates that one entity is a surface-level characteristic, pattern, or feature belonging to or present on another entity.
-
B.
hasSurfaceFeatureState
Indicates that an entity currently exhibits a particular condition or status of one of its surface features.
-
C.
visualFeature
Indicates a relationship where one entity possesses or exhibits a particular visual characteristic or attribute of another entity.
-
D.
textureFeatures
Indicates that one entity possesses or is characterized by specific surface or material texture properties described by the other entity.
-
E.
imagedIn
Indicates that one entity appears within or is depicted in an image associated with another entity.
- 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_69da627278c88190babe4297a9df1236 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6632c085081908710cbc939ac9971 |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:37 p.m.