Triple
T17627549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aichi M6A |
E429887
|
entity |
| Predicate | designedForLaunchFrom |
P114408
|
FINISHED |
| Object | submarines |
—
|
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: submarines | Statement: [Aichi M6A, designedForLaunchFrom, submarines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedForLaunchFrom Context triple: [Aichi M6A, designedForLaunchFrom, submarines]
-
A.
designedToBeLaunchedFrom
chosen
Indicates that one entity is specifically created or configured for the purpose of being launched from another entity.
-
B.
usedForLaunchOf
Indicates that something serves as the means, tool, or platform by which a launch (such as of a product, mission, or event) is carried out.
-
C.
usesLaunchVehicleCore
Indicates that a space mission or launch event makes use of a specific launch vehicle core as part of its propulsion or structural stack.
-
D.
usesLaunchVehiclesFrom
Indicates that one entity conducts its launches by employing launch vehicles that originate from or are provided by another entity.
-
E.
launchedWith
Indicates that one entity was initiated, started, or set into motion together with another entity as part of the same launch event.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46dbe3a308190a818d04f1a9b15f7 |
completed | April 19, 2026, 5:53 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 5:52 a.m.