Triple
T20114604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Venera 11 |
E490423
|
entity |
| Predicate | orbitalFlyby |
P104764
|
FINISHED |
| Object | performed by carrier bus after probe release |
—
|
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: performed by carrier bus after probe release | Statement: [Venera 11, orbitalFlyby, performed by carrier bus after probe release]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitalFlyby Context triple: [Venera 11, orbitalFlyby, performed by carrier bus after probe release]
-
A.
flybyOrOrbiter
chosen
Indicates that one entity performs a close pass or maintains an orbital trajectory around another entity without landing on it.
-
B.
flybyOf
Indicates that one entity passes close to another in space without stopping, typically as part of an observational or transit maneuver.
-
C.
thirdFlybyBody
Indicates that an object performs or experiences a third flyby maneuver relative to a specified celestial body.
-
D.
earthFlybyPurpose
Indicates that an Earth flyby maneuver is performed with a specific intended purpose or objective, such as trajectory adjustment, gravity assist, or mission optimization.
-
E.
secondFlybyBody
Indicates that an entity serves as the second celestial body encountered during a flyby trajectory or mission.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666e3f2288190840d1eb431ac9a1b |
completed | April 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:29 p.m.