Triple
T28524106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | O-rings |
E721861
|
entity |
| Predicate | hasFailureMode |
P134465
|
FINISHED |
| Object | extrusion |
—
|
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: extrusion | Statement: [O-rings, hasFailureMode, extrusion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFailureMode Context triple: [O-rings, hasFailureMode, extrusion]
-
A.
hasFailureProbability
Indicates that an entity is associated with a likelihood or chance that it will fail within a given context or conditions.
-
B.
hasFailureProbabilitySymbol
Indicates that an entity is associated with a symbolic representation of its probability of failure.
-
C.
launchFailureMode
Indicates the specific way in which a launch attempt fails or the type of failure that occurs during a launch.
-
D.
failureModel
chosen
Indicates the type or structure of how a system, component, or process can fail or behaves when failures occur.
-
E.
hasCompatibilityMode
Indicates that one entity operates under a special mode or setting designed to maintain compatibility with another entity or with an earlier version.
- 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_69f01a5cbcc4819083fb4e723378713e |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f7221dc9a88190bb8194fcc29c42bc |
completed | May 3, 2026, 10:23 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
Created at: April 28, 2026, 3:23 a.m.