Triple
T20895915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WR-40 Langusta |
E514533
|
entity |
| Predicate | launcherElevation |
P97736
|
FINISHED |
| Object | variable |
—
|
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: variable | Statement: [WR-40 Langusta, launcherElevation, variable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launcherElevation Context triple: [WR-40 Langusta, launcherElevation, variable]
-
A.
launchAzimuth
Indicates the directional angle or bearing along which a launch (such as a rocket or missile) is initiated relative to a reference direction.
-
B.
launchVehicleUser
Indicates that one entity uses or operates a particular launch vehicle to carry out a launch or space mission.
-
C.
launchVehicle
Indicates that one entity serves as the rocket or carrier used to launch another entity (such as a payload, spacecraft, or mission) into space or a target trajectory.
-
D.
launcherType
Indicates the specific kind or category of launcher associated with or used in relation to an entity.
-
E.
elevationHolder
chosen
Indicates that one entity serves as the reference or container for the elevation (height above a baseline) 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6d06233588190942493b709e30820 |
completed | April 21, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c9ac91108190a6700fcdf2f11890 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:47 p.m.