Triple
T23944929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VHB Tape |
E602887
|
entity |
| Predicate | isDoubleSided |
P35793
|
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, isDoubleSided, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDoubleSided Context triple: [VHB Tape, isDoubleSided, true]
-
A.
isDoubleCoverOf
Indicates that one object serves as a two-to-one covering of another, such that each point or element of the second is covered by exactly two corresponding points or elements of the first.
-
B.
isDoubleAAsideWith
Indicates that two entities are paired together as a double A-side, typically sharing equal prominence in a joint release (such as two lead tracks on the same single).
-
C.
hasTwoMainFaces
chosen
Indicates that an entity possesses exactly two primary or most prominent faces or sides.
-
D.
storageCapacityDualLayerDoubleSided
Indicates the total data storage capacity of a medium that uses dual layers on both sides (double-sided) for recording.
-
E.
hasDualSpace
Indicates that one mathematical space is the dual space consisting of all linear functionals defined on another space.
- 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_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. |
Created at: April 17, 2026, 9:11 p.m.