Triple
T4080328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vanguard TV-4 |
E87461
|
entity |
| Predicate | orbitTypeAchieved |
P7214
|
FINISHED |
| Object | low Earth 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: low Earth orbit | Statement: [Vanguard TV-4, orbitTypeAchieved, low Earth orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orbitTypeAchieved Context triple: [Vanguard TV-4, orbitTypeAchieved, low Earth orbit]
-
A.
orbitType
chosen
Indicates the specific kind or classification of an object's orbit in relation to the body it revolves around.
-
B.
orbitReached
Indicates that an object has successfully arrived at and is now following its intended orbital path around a central body.
-
C.
orbitCapability
Indicates that one entity has the ability or suitability to orbit around another entity.
-
D.
successfullyReachedOrbitOnVehicle
Indicates that an entity has successfully achieved orbit using a specified launch vehicle.
-
E.
orbiterDesignation
Indicates that one entity is designated as an orbiter (spacecraft or object in orbit) associated with another entity.
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc5087b081909d6042bfe8d8a306 |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9082c2081908474f082a49bebc8 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:39 p.m.