Triple
T37072989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PS4 |
E917630
|
entity |
| Predicate | positionInLaunchVehicle |
P201026
|
FINISHED |
| Object | fourth stage |
—
|
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: fourth stage | Statement: [PS4, positionInLaunchVehicle, fourth stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInLaunchVehicle Context triple: [PS4, positionInLaunchVehicle, fourth stage]
-
A.
usedByLaunchVehicle
Indicates that something (such as equipment, infrastructure, or a resource) is utilized by a specific launch vehicle during its operations.
-
B.
positionOnAircraft
Indicates that one entity occupies a specific seat or location on an aircraft in relation to that aircraft.
-
C.
coordinatesSpacecraft
Indicates overseeing and directing the movement and positioning of a spacecraft within its operational space.
-
D.
locationOnSpacecraft
Indicates that one entity occupies or is situated at a specific place or position on a spacecraft.
-
E.
hasVerticalLaunchSystem
Indicates that one entity is equipped with a vertical launch system used to fire missiles or similar munitions vertically.
- 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_69f76e9771e08190a690834e3cd20654 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffc1550cb481908628e446d9b67f7b |
completed | May 9, 2026, 11:20 p.m. |
| PD | Predicate disambiguation | batch_69ffc10a74708190ae90e2c378791f70 |
completed | May 9, 2026, 11:19 p.m. |
| PDg | Predicate description generation | batch_69ffc15434c8819093aa3b33813613be |
completed | May 9, 2026, 11:20 p.m. |
Created at: May 3, 2026, 4:14 p.m.