Triple
T4001017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sputnik 1 |
E89412
|
entity |
| Predicate | timeInOrbit_days |
P53433
|
FINISHED |
| Object | about 92 |
—
|
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: about 92 | Statement: [Sputnik 1, timeInOrbit_days, about 92]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInOrbit_days Context triple: [Sputnik 1, timeInOrbit_days, about 92]
-
A.
hasOrbitalPeriod
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.
minimumOrbitIntersectionDistanceWithEarth_au
Indicates the smallest distance, measured in astronomical units, between an object's orbit and Earth's orbit at their closest point of approach.
-
D.
hasAverageYearLength
Indicates that one entity has a specified average duration for its year (orbital period), typically measured over time.
-
E.
orbitType
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
- 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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa8579288190940487ad07e38de0 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8f89f2881909b0965419d15d46c |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefa815f2c8190818c9ffd9d1bf478 |
completed | March 9, 2026, 4:51 p.m. |
Created at: March 9, 2026, 3:34 p.m.