Triple
T16720081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vanguard rocket |
E406323
|
entity |
| Predicate | designedToPlace |
P124366
|
FINISHED |
| Object | 2.3-kilogram satellite into 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: 2.3-kilogram satellite into orbit | Statement: [Vanguard rocket, designedToPlace, 2.3-kilogram satellite into orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToPlace Context triple: [Vanguard rocket, designedToPlace, 2.3-kilogram satellite into orbit]
-
A.
designedForLocation
Indicates that something has been created or configured specifically to be used in, or suited to, a particular location.
-
B.
hasPlaceIn
Indicates that one entity occupies, is located within, or holds a specific position in another entity or context.
-
C.
targetedPlace
Indicates that an entity intentionally directed an action, operation, or influence toward a specific place or location.
-
D.
canBePlacedUnder
Indicates that one entity is allowed or able to be positioned beneath another entity in a spatial or structural arrangement.
-
E.
designedIn
Indicates that something was created, planned, or conceived during a particular time period or at a specific location.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3874270748190ad7c3b3531293b60 |
completed | April 18, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:20 a.m.