Triple
T8673514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LauncherOne |
E205857
|
entity |
| Predicate | massToSunSynchronousOrbit |
P84009
|
FINISHED |
| Object | approximately 300 kg |
—
|
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: approximately 300 kg | Statement: [LauncherOne, massToSunSynchronousOrbit, approximately 300 kg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: massToSunSynchronousOrbit Context triple: [LauncherOne, massToSunSynchronousOrbit, approximately 300 kg]
-
A.
massInJupiterOrbit
Indicates the mass an object has while it is located in orbit around Jupiter.
-
B.
massRelativeToMoon
Indicates that one entity’s mass is being expressed as a value relative to, or in comparison with, the mass of the Moon.
-
C.
centralBody
Indicates that one object serves as the primary gravitational or reference body around which another object orbits or is defined.
-
D.
meanSurfaceGravity_m_per_s2
Indicates the average gravitational acceleration experienced at the surface of an object, measured in meters per second squared.
-
E.
massRelativeToEarth
Indicates the comparative amount of mass an entity has relative to the mass of Earth.
- 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_69ca83529a9c8190b5c075b4f14636ed |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc491b807c81909563a34a947bc21a |
completed | March 31, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:31 p.m.