Triple
T1073287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaga-class aircraft carrier |
E23377
|
entity |
| Predicate | aircraftLaunchAndRecovery |
P23968
|
FINISHED |
| Object | STOVL operations |
—
|
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: STOVL operations | Statement: [Kaga-class aircraft carrier, aircraftLaunchAndRecovery, STOVL operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftLaunchAndRecovery Context triple: [Kaga-class aircraft carrier, aircraftLaunchAndRecovery, STOVL operations]
-
A.
launchedAircraftIn
Indicates that an entity initiated the takeoff or deployment of an aircraft within a specified location or context.
-
B.
airRefuellingMethod
Indicates the method or technique used to transfer fuel between aircraft during in-flight refuelling.
-
C.
aircraft
Indicates that an entity is an aircraft or functions in the role of an aircraft in the described context.
-
D.
landingGear
Indicates that an entity’s landing gear is present, deployed, or otherwise involved in a landing-related state or action relative to another entity or context.
-
E.
plannedLandingMethod
Indicates that an entity has designated a specific method or procedure to be used for its landing.
- 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_69a493ee1f908190992b5f0d1b04459b |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b92afad88190b7705923f71fc760 |
completed | March 1, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69a4b73844708190a16c9e9824ca2fb6 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b8d5076481908640a0d873efdf14 |
completed | March 1, 2026, 10:08 p.m. |
Created at: March 1, 2026, 7:42 p.m.