Triple
T33660402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R91 Charles de Gaulle |
E862334
|
entity |
| Predicate | aircraftCatapultType |
P37363
|
FINISHED |
| Object | steam catapult |
—
|
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: steam catapult | Statement: [R91 Charles de Gaulle, aircraftCatapultType, steam catapult]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftCatapultType Context triple: [R91 Charles de Gaulle, aircraftCatapultType, steam catapult]
-
A.
catapultType
chosen
Indicates the specific kind or category of catapult associated with an entity or event.
-
B.
aircraftLaunchAndRecovery
Indicates the relationship in which an aircraft is launched from and/or recovered by a platform, facility, or system.
-
C.
launchedAircraftIn
Indicates that an entity initiated the takeoff or deployment of an aircraft within a specified location or context.
-
D.
poweredAircraftType
Indicates that one entity is a type or category of aircraft that is propelled by an onboard power source (e.g., engines), as opposed to being unpowered.
-
E.
usesCarrierAircraft
Indicates that one entity employs or operates aircraft that are designed to be launched from and recovered by an aircraft carrier.
- 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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:42 a.m.