Triple
T30357609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DD series |
E772189
|
entity |
| Predicate | mechanicalIssue |
P155623
|
FINISHED |
| Object | center gear cracking in some models |
—
|
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: center gear cracking in some models | Statement: [DD series, mechanicalIssue, center gear cracking in some models]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mechanicalIssue Context triple: [DD series, mechanicalIssue, center gear cracking in some models]
-
A.
mechanicalExpertise
Indicates that one entity possesses specialized knowledge or skill in understanding, operating, or repairing mechanical systems or devices in relation to another entity or context.
-
B.
equipmentIssue
chosen
Indicates that there is a problem, malfunction, or defect affecting a piece of equipment.
-
C.
propulsionIssue
Indicates that there is a problem, malfunction, or abnormal condition affecting an entity’s propulsion system or propulsion-related performance.
-
D.
mechanicalFunction
Indicates that one entity serves as the mechanical role, operation, or function performed by another entity or system.
-
E.
engineFailure
Indicates that an engine has malfunctioned or ceased to operate as intended.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6823fe8c48190a8911627f79dd949 |
completed | May 2, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:57 p.m.