Triple
T2139192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geosynchronous Satellite Launch Vehicle |
E46721
|
entity |
| Predicate | typicalPayloadToGTO |
P12525
|
FINISHED |
| Object | about 2 tonnes |
—
|
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 2 tonnes | Statement: [Geosynchronous Satellite Launch Vehicle, typicalPayloadToGTO, about 2 tonnes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPayloadToGTO Context triple: [Geosynchronous Satellite Launch Vehicle, typicalPayloadToGTO, about 2 tonnes]
-
A.
payloadToGTO
chosen
Indicates the maximum mass a launch system can deliver into a geostationary transfer orbit (GTO).
-
B.
plannedPayload
Indicates that an entity is designated or scheduled to be carried, delivered, or transported as part of a planned operation or mission.
-
C.
payloadToTLI
Indicates that a payload is transferred or propelled from its initial orbit or trajectory into a Trans-Lunar Injection (TLI) trajectory toward the Moon.
-
D.
payloadTo700kmSSO
Indicates the capability or action of delivering a payload into a 700-kilometer altitude sun-synchronous orbit (SSO).
-
E.
payloadType
Indicates the kind or category of payload associated with or carried by an entity or action.
- 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_69a88a174ab48190a5db20c132e5dccf |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbf74147c81908793c3694894f94a |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbd96a3b0819081efbfef975e1513 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:44 p.m.