Triple
T1927139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vostok 1 |
E40857
|
entity |
| Predicate | orbitalPeriodMinutes |
P2028
|
FINISHED |
| Object | approx 89 |
—
|
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 89 | Statement: [Vostok 1, orbitalPeriodMinutes, approx 89]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitalPeriodMinutes Context triple: [Vostok 1, orbitalPeriodMinutes, approx 89]
-
A.
hasOrbitalPeriod
chosen
Indicates that one entity completes a full orbit around another entity within a specified duration.
-
B.
hasRotationPeriod
Indicates that one entity has a specified duration for completing a full rotation around its own axis.
-
C.
orbitalEccentricity
Indicates the degree to which an orbit deviates from a perfect circle, quantifying how elongated the orbital path is.
-
D.
averageOrbitalSpeed
Indicates the typical speed at which one celestial body travels along its orbit around another over a complete orbital period.
-
E.
hasOrbitalResonanceWith
Indicates that two orbiting bodies have orbital periods in a simple integer ratio, causing their gravitational influences to repeat in a regular, synchronized pattern.
- 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_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. |
Created at: March 4, 2026, 7:35 p.m.