Triple
T22457586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Failure Mode and Effects Analysis |
E555154
|
entity |
| Predicate | isApproachType |
P10782
|
FINISHED |
| Object | systematic |
—
|
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: systematic | Statement: [Failure Mode and Effects Analysis, isApproachType, systematic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isApproachType Context triple: [Failure Mode and Effects Analysis, isApproachType, systematic]
-
A.
hasApproachType
chosen
Indicates the specific method, strategy, or manner in which an action, process, or interaction is carried out or approached.
-
B.
hasApproachSide
Indicates that one entity has a particular side or direction from which another entity can approach or access it.
-
C.
usedToApproach
Indicates that one entity employed another entity as a means or method to move closer to or reach a target entity or location.
-
D.
isMajorApproachTo
Indicates that one method, route, or strategy serves as a primary or principal way of reaching, addressing, or dealing with another entity.
-
E.
hasApproachFeature
Indicates that something possesses a characteristic, element, or quality specifically related to its method, strategy, or manner of approach.
- 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_69e11e51fdec8190adfdf9f8a6362221 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b7d00208190955a70e2c22d25a4 |
completed | April 29, 2026, 1:14 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.