Triple
T33553890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaika |
E859412
|
entity |
| Predicate | usedOnOrbitsCount |
P50723
|
FINISHED |
| Object | multiple Earth orbits |
—
|
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: multiple Earth orbits | Statement: [Chaika, usedOnOrbitsCount, multiple Earth orbits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedOnOrbitsCount Context triple: [Chaika, usedOnOrbitsCount, multiple Earth orbits]
-
A.
orbitsUsed
Indicates that one entity utilizes or traverses specific orbital paths associated with another entity.
-
B.
orbitsCovered
chosen
Indicates that one entity completes or spans a specified number of orbital revolutions around another entity.
-
C.
numberOfOrbitsPlanned
Indicates the planned count of orbital revolutions or passes an object is expected to complete.
-
D.
numberOfOrbitalPlanes
Indicates the specific count of distinct orbital planes associated with an object or system.
-
E.
designedForOrbitType
Indicates that something is specifically created or configured to operate within a particular type or class of orbit.
- 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_69f3497b2b68819093207971b5e13dc8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f70c17d88190aa74afc2dd2a0467 |
completed | May 3, 2026, 7:19 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:40 a.m.