Triple
T18274337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KVTK |
E437694
|
entity |
| Predicate | usedForOrbitInsertion |
P45583
|
FINISHED |
| Object | geostationary transfer orbit |
—
|
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: geostationary transfer orbit | Statement: [KVTK, usedForOrbitInsertion, geostationary transfer orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForOrbitInsertion Context triple: [KVTK, usedForOrbitInsertion, geostationary transfer orbit]
-
A.
designedForOrbitInsertion
chosen
Indicates that something is intended or configured to perform or facilitate the insertion of an object into orbit.
-
B.
orbitalInsertionAround
Indicates the action or event of placing an object into a stable orbit around another body.
-
C.
designedForOrbitType
Indicates that something is specifically created or configured to operate within a particular type or class of orbit.
-
D.
orbitInsertionAttempt
Indicates an attempt to place an object into a stable orbit around a celestial body.
-
E.
orbitInjectionMethod
Indicates the method or technique used to insert an object into a specific 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50050d6688190b909a1c24e1dd3c9 |
completed | April 19, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.