Triple
T9179923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mechanical Systems |
E220294
|
entity |
| Predicate | hasKeyAttribute |
P14117
|
FINISHED |
| Object | safety-critical design |
—
|
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: safety-critical design | Statement: [Mechanical Systems, hasKeyAttribute, safety-critical design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyAttribute Context triple: [Mechanical Systems, hasKeyAttribute, safety-critical design]
-
A.
hasKeyElement
Indicates that one entity contains or depends on another entity that serves as a primary or essential component.
-
B.
hasKeyRelationship
Indicates a relationship where one entity serves as a key (e.g., identifier, access token, or primary reference) that grants access to, controls, or uniquely identifies another entity.
-
C.
hasKeyAspect
chosen
Indicates that something possesses a central, defining, or particularly important feature or characteristic.
-
D.
hasKeyCapability
Indicates that an entity possesses an essential ability or function that is critical for performing a particular task or role.
-
E.
hasKeyFunction
Indicates that one entity serves as a primary or essential function or role for another entity.
- 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_69ca83e589948190ac9907819db11ddf |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccc251da448190a5c7f684dac15a84 |
completed | April 1, 2026, 6:59 a.m. |
| PD | Predicate disambiguation | batch_69cc66090e5881908889dc1213815626 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:23 p.m.