Triple
T1927146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vostok 1 |
E40857
|
entity |
| Predicate | cosmonautEjectionAltitudeKm |
P33548
|
FINISHED |
| Object | approx 7 |
—
|
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: approx 7 | Statement: [Vostok 1, cosmonautEjectionAltitudeKm, approx 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cosmonautEjectionAltitudeKm Context triple: [Vostok 1, cosmonautEjectionAltitudeKm, approx 7]
-
A.
orbitAltitude
Indicates the height of an object's orbit above a reference body, typically measured from the body's surface or mean radius.
-
B.
explosionAltitude
Indicates the height above a reference surface at which an explosion occurs or is triggered.
-
C.
orbitApogee
Indicates the point in an orbit where an orbiting body is farthest from the central body it revolves around.
-
D.
hasAltitudeOfDetonation
Indicates that an explosive event or detonation occurs at a specified altitude above a reference level (typically ground or sea level).
-
E.
reachedApogee
Indicates that an object in orbit has arrived at the highest point (apogee) in its trajectory around a central body.
- 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_69a8864711648190b07bed24ed76258e |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb263cdb8819084d0bda98a2a71e0 |
completed | March 7, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_69abafeec6f881909d47acb966683279 |
completed | March 7, 2026, 4:56 a.m. |
| PDg | Predicate description generation | batch_69abb20c4970819086e66a5435744297 |
completed | March 7, 2026, 5:05 a.m. |
Created at: March 4, 2026, 7:35 p.m.