Triple
T6140285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LR-91 |
E136942
|
entity |
| Predicate | usedForLaunchOf |
P69408
|
FINISHED |
| Object | military satellites |
—
|
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: military satellites | Statement: [LR-91, usedForLaunchOf, military satellites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForLaunchOf Context triple: [LR-91, usedForLaunchOf, military satellites]
-
A.
launchedWith
Indicates that one entity was initiated, started, or set into motion together with another entity as part of the same launch event.
-
B.
launchedTo
Indicates that one entity has been sent or propelled from its origin toward a specific target or destination.
-
C.
launchesFrom
Indicates that an object or agent initiates its movement, operation, or departure starting at a specified location or source.
-
D.
usesLaunchVehicleCore
Indicates that a space mission or launch event makes use of a specific launch vehicle core as part of its propulsion or structural stack.
-
E.
usesLaunchSite
Indicates that an entity conducts or carries out its launches from a particular launch site.
- 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_69c008a179388190a3b5a081bbf46d55 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05cb030fc8190b78e4967eea65611 |
completed | March 22, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69c055f19b0c81908be34a00ab218723 |
completed | March 22, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69c056c87340819088003f427706ebf8 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:15 p.m.