Triple
T22646701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitsubishi Aircraft Corporation |
E558981
|
entity |
| Predicate | programIssue |
P149049
|
FINISHED |
| Object | multiple schedule delays |
—
|
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: multiple schedule delays | Statement: [Mitsubishi Aircraft Corporation, programIssue, multiple schedule delays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programIssue Context triple: [Mitsubishi Aircraft Corporation, programIssue, multiple schedule delays]
-
A.
platformIssue
Indicates that there is a problem, malfunction, or limitation affecting the operation or availability of a platform.
-
B.
program
Indicates that an entity creates, writes, or develops a computer program or software application.
-
C.
programCostIssue
Indicates that there is a problem, concern, or irregularity related to the cost of a program.
-
D.
possibleIssue
Indicates that there is a potential or suspected problem, defect, or undesired condition associated with the referenced entity or situation, though it is not yet confirmed.
-
E.
programChallenge
Indicates that an entity sets or presents a programming-related task or problem for another entity to solve or complete.
- 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_69e24547f7fc819086e2c4ba3b979657 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f170382ba48190b77692762db43313 |
completed | April 29, 2026, 2:43 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8841e9cc81908d23b34215e3be71 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:05 p.m.