Triple
T26474396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bridgman anvil cell |
E665987
|
entity |
| Predicate | pressureTransmission |
P162160
|
FINISHED |
| Object | solid medium |
—
|
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: solid medium | Statement: [Bridgman anvil cell, pressureTransmission, solid medium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pressureTransmission Context triple: [Bridgman anvil cell, pressureTransmission, solid medium]
-
A.
pressureType
Indicates the specific category or kind of pressure associated with an entity or interaction.
-
B.
pressureCapability
Indicates the maximum pressure an entity can safely exert, withstand, or operate under within a given context.
-
C.
pressureFrom
Indicates a relationship where one entity exerts influence, coercion, or force on another to affect its decisions, actions, or state.
-
D.
pressureContext
Indicates a situational or environmental condition in which entities experience or exert pressure, stress, or constraint on one another or on a shared context.
-
E.
pressurization
Indicates the process of applying or maintaining pressure on or within an object, system, or environment.
- F. None of above. chosen
Provenance (4 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_69ee883f80dc819090e311b022b78e02 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 27, 2026, 12:22 a.m.