Triple
T23944931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VHB Tape |
E602887
|
entity |
| Predicate | isPressureSensitive |
P154447
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [VHB Tape, isPressureSensitive, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPressureSensitive Context triple: [VHB Tape, isPressureSensitive, true]
-
A.
hasApproximatePressure
Indicates that one entity has a pressure value that is approximately equal to the pressure value associated with another entity or reference.
-
B.
isPressingOf
Indicates that one entity is applying pressure or force onto another entity.
-
C.
hasShiftPressureFrom
Indicates that one entity experiences or is subjected to shift-related pressure originating from another entity.
-
D.
hasHumanPressure
Indicates that one entity exerts or experiences human-induced influence, stress, or impact in relation to another entity or environment.
-
E.
hasPressureSphere
Indicates a relationship where an entity possesses or is associated with a defined region or volume characterized by a specific pressure condition.
- 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d02d07b08190acbcbb646cd9a58e |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 9:11 p.m.