Triple
T9299217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Macon (ZRS-5) |
E223717
|
entity |
| Predicate | aircraftLaunchRecoverySystem |
P23968
|
FINISHED |
| Object | trapeze system |
—
|
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: trapeze system | Statement: [USS Macon (ZRS-5), aircraftLaunchRecoverySystem, trapeze system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftLaunchRecoverySystem Context triple: [USS Macon (ZRS-5), aircraftLaunchRecoverySystem, trapeze system]
-
A.
aircraftLaunchAndRecovery
chosen
Indicates the relationship in which an aircraft is launched from and/or recovered by a platform, facility, or system.
-
B.
launchVehicleCoreRecovery
Indicates that the core stage of a launch vehicle is recovered after launch rather than being expended.
-
C.
hasVerticalLaunchSystem
Indicates that one entity is equipped with a vertical launch system used to fire missiles or similar munitions vertically.
-
D.
spacecraftRecoveryBy
Indicates that a spacecraft is retrieved or recovered by a specified agent, such as an organization, mission, or system.
-
E.
parachuteSystem
Indicates that one entity functions as a parachute system used to safely decelerate or recover 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd08cf50cc8190a025f478dff4f9fd |
completed | April 1, 2026, noon |
| PD | Predicate disambiguation | batch_69cc7a5ef1908190bc5ca166bb895af6 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:36 p.m.