Triple
T13202960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5.56×45mm NATO |
E314285
|
entity |
| Predicate | hasMaximumPressure |
P56372
|
FINISHED |
| Object | 430 MPa |
—
|
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: 430 MPa | Statement: [5.56×45mm NATO, hasMaximumPressure, 430 MPa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximumPressure Context triple: [5.56×45mm NATO, hasMaximumPressure, 430 MPa]
-
A.
hasHumanPressure
Indicates that one entity exerts or experiences human-induced influence, stress, or impact in relation to another entity or environment.
-
B.
pressureCapability
chosen
Indicates the maximum pressure an entity can safely exert, withstand, or operate under within a given context.
-
C.
hasPressureSphere
Indicates a relationship where an entity possesses or is associated with a defined region or volume characterized by a specific pressure condition.
-
D.
hasMaximumThickness
Indicates that an entity possesses a specified upper limit on its thickness.
-
E.
hasShiftPressureFrom
Indicates that one entity experiences or is subjected to shift-related pressure originating from 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc6bc108190b5a6a265bf6e9fd4 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:16 p.m.