Triple
T19543097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venera 10 |
E488958
|
entity |
| Predicate | landerFunction |
P136719
|
FINISHED |
| Object | surface imaging |
—
|
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: surface imaging | Statement: [Venera 10, landerFunction, surface imaging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landerFunction Context triple: [Venera 10, landerFunction, surface imaging]
-
A.
landerProvider
Indicates the organization or entity responsible for providing or operating the lander used in a mission or operation.
-
B.
loreFunction
Indicates that something serves a narrative or world-building role within a fictional or informational context.
-
C.
landingPilot
Indicates that an entity is acting as the pilot responsible for landing an aircraft or spacecraft.
-
D.
shipFunction
Indicates that one entity serves as the functional role, purpose, or operational use of a ship.
-
E.
navigationFunction
Indicates a relationship where one entity serves as a guide or mapping that determines how another entity moves or progresses through a space, system, or state.
- 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e638750b288190aecdb0e18a1add62 |
completed | April 20, 2026, 2:30 p.m. |
| PD | Predicate disambiguation | batch_69e514c9c00481909b76bda67957e58b |
completed | April 19, 2026, 5:45 p.m. |
| PDg | Predicate description generation | batch_69e51a23300c8190988552491d9783d7 |
completed | April 19, 2026, 6:08 p.m. |
Created at: April 10, 2026, 1:41 p.m.